dotty VS Metals

Ahhh no unused warnings, thats disappointing to say the least. I guess some progress is being made here https://github.com/lampepfl/dotty/pull/16157 , tbh this kind of stuff makes me want to stick to Scala 2.

We just released the new version of ScalaDoc for the standard library API for 3.2.1. I hope you will like it, it contains a lot of changes! https://www.scala-lang.org/api/3.2.1/index.html If you are interested in what exactly was changed, take a look at this PR: https://github.com/lampepfl/dotty/pull/16310

There is quite an old issue on this topic on dotty: https://github.com/lampepfl/dotty/issues/2573 (Nothing (or almost nothing) changed)

Linting for unused stuff is being worked on, see https://github.com/lampepfl/dotty/pull/16157. Hopefully it'll land soon.

Then start playing with reflection API - I suggest having Quotes opened in your IDE, and documentation in your browser. Use showRaw to print expressions you constructed - it will help you understand how to build from ground up when you cannot build something using only expressions.

This was taken care of recently: https://github.com/lampepfl/dotty/pull/15540/files

A more limited way to do runtime evaluation is via the jsr-223 support: https://github.com/lampepfl/dotty/blob/main/tests/run-with-compiler/scripting.scala, you can't reflect on types that way but the advantage is that you don't end up depending on compiler-internals APIs that could change in any patch release.

https://github.com/lampepfl/dotty/issues/14262 points to https://github.com/invesdwin/invesdwin-context/blob/master/invesdwin-context-parent/invesdwin-context-scala/src/main/java/de/invesdwin/context/scala/pool/WrappedScalaScriptEngine.java which seems to be doing some caching via https://docs.oracle.com/javase/8/docs/api/javax/script/Compilable.html, but I have zero experience with this stuff.

Please write in the comments if you know of any language servers I should test it with. Currently I tested only metals and rust-analyzer.

If you are using nvim-lspconfig you can pass the settings as a Lua table to the setup function. For example, here are may metals settings:

Bazel support in Metals. I didn't spend all that time figuring out and adjusting Emacs/Spacemacs and making my workflow (almost) mouse-free just to scrap my config and switch to IDEA's rodent infested ways.

There is one small issue involving code completion returning inappropriate completions in some cases; https://github.com/scalameta/metals/pull/4414 will fix it, once it's included in a release. Perhaps that's the PR you saw?

It is, by quite a bit.

While the "Scala IDE" project is dead for all practical purposes, IntelliJ IDEA's Scala plugin is actually pretty amazing. There's also a VisualStudio plugin that does pretty much the same and is advancing by leaps and bounds. There are also interconnecting projects that provide i.e. language server or build server that are reused by other projects. It's pretty modular. Metals (https://scalameta.org/metals/) is amazing.

In general the language has become a wee bit faster to build, there was good progress with build times during the 2.12/2.13 cycles.

With Scala3 the language got a bit simpler; concepts that were implemented explicitly using (hehe) implicits got their own keywords and a lot of the opinionated boilercode that cause a lot of debates is now generated during complication and hidden. A lot of "standardization" has occurred.

Have a look at https://scalameta.org/metals/

You should be able to use Metals with vim and get IDE-like functionalities in your preferred editor: https://scalameta.org/metals/

Once we have that, we can import the project into IntelliJ or Metals.