Seth Tisue

> in class mode, treat objects and traits as classes as well so that companions are grouped together @jrudolph fwiw, if you (or anyone else watching this repo) PRed that...

the dot generation part would probably be more useful if we had source-file-level and package-level aggregation

deja vu :-) https://contributors.scala-lang.org/t/sculpt-dependency-graph-extraction-for-scala/1507/3 yes, I think this is a modest, doable change, and if you get stuck, I'd be happy to help get you unstuck.

@johnynek I'm sorry I haven't managed to reply to you about this yet :-( it's very near the top of my queue, I'm just a little overwhelmed right now with...

what do you think about a different approach where instead of adding new edges, we just change ``` case class Entity(name: String, kind: EntityKind) ``` to ``` case class Entity(name:...

(I'll have to think about this in early January.)

@johnynek yeah, I like your way, I'm convinced. happy to merge this if you can get CI to sign off.

would using sbt 0.13.17-RC2 or 1.1.0 make the need for this disappear? (surely there's an sbt/sbt issue number on this?)

the sbt version is determined here https://github.com/underscoreio/creative-scala/blob/develop/project/build.properties I'm afraid I'm not familiar with jenv. my own method of switching Java versions on MacOS is to do e.g. `export JAVA_HOME=$(/usr/libexec/java_home -v...

(we're at ScalaBridge Montreal right now, @ironfish had the same reaction, that this syntax shouldn't be used to start with, or if it is used, should at least be explained...