Ólafur Páll Geirsson

The scalafmt cli currently uses parallel collections which I suspect use JVM concurrency features. To link the cli in native it probably needs a bit of refactoring.

For people interested in native scalafmt, please give the branch in https://github.com/scalameta/scalafmt/pull/1266 a try and report back how it works :)

@guizmaii thank you for reporting! As a workaround, it should be possible to only depend on scalafmt-interfaces and dynamically classload scalafmt-dynamic. I believe this is what the Gradle spotless integration...

@jrudolph Thank you so much for this thorough investigation. I believe the Scalamt codebase is ripe for microoptimizations 👍 The code was written when I was just starting Scala a...

You can generate flame graphs with https://github.com/jvm-profiling-tools/async-profiler

My apologies for the slow response. Originally, Scalameta was founded to become a better macro system for Scala but over time we shifted focus to developer tools (like scalafix/scalafmt) and...

Thank you for reporting! Seems like this might get fixed by using `executableName` here instead of `"src"` https://github.com/sourcegraph/src-cli/blob/main/npm-distribution/install.js#L59 I'll try to reproduce and fix on my Windows computer

NB, I just opened https://github.com/scalameta/metals/pull/236 to enable hover by default. It used to be disabled when hover relied on the presentation compiler but now it uses SemanticDB, the same as...

The VS Code plugin package.json for some reason enabled it by default so I didn't notice it was off in other clients.

@emirot Thank you for reporting! I opened a PR https://github.com/sourcegraph/lsif-java/pull/381 documenting how to change the default Java version in the Docker container. You can change the java version with `eval...