-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
asTerm called on not-a-Term val <none>
thrown when compiling Dotty via Bloop
#2517
Comments
If I disable inlay hints, I get the same error from a different place:
|
mbovel
changed the title
Dotty with Bloop:
Nov 26, 2024
scala3-compiler
getting recompiled over and overasTerm called on not-a-Term val <none>
thrown the compiling Dotty through Bloop
mbovel
changed the title
Nov 26, 2024
asTerm called on not-a-Term val <none>
thrown the compiling Dotty through BloopasTerm called on not-a-Term val <none>
thrown when compiling Dotty via Bloop
Well, I:
and now |
Could it be an issue with incremental compilation? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just cloned Dotty (at scala/scala3@c3d6c48) on a new Ubuntu machine and tried to use Bloop as the build server.
Metals seems to work: I can go to symbol, read doc, I have inlay type hints (😍), etc.
However, if I go to
compiler/src/dotty/tools/dotc/typer/Typer.scala
every time I save, even if I do no changes,scala3-compiler
is recompiled entirely (~30 seconds approximately on this fast machine, would take 4 times more on my laptop):Looking further:
There are errors reported in
compiler/src/dotty/tools/dotc/sbt/interfaces/ProgressCallback.java
anddotty/tools/dotc/sbt/interfaces/ProgressCallback.java
:Compilation of
scala3-compiler
fails with a compiler crash:assertion failed: asTerm called on not-a-Term val <none>
:Debug files:
The text was updated successfully, but these errors were encountered: