Skip to content

Emit mixin-related methods as artifacts, mixin forwarders as bridges #6141

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

Merged
merged 3 commits into from
Mar 22, 2019

Conversation

smarter
Copy link
Member

@smarter smarter commented Mar 21, 2019

And in the process fix the language server (see #6128)

Mixin forwarders are now emitted unconditionally and without generic
signatures, this broke lsp4j and therefore our language server, emitting
mixin forwards with the Artifact flag (which remember corresponds to
SYNTHETIC in Java bytecode) unbreaks lsp4j, and it seems reasonable to
use this for all the forwarders we generate for traits, including
super-accessors.
@smarter smarter requested a review from odersky March 21, 2019 16:46
@smarter smarter force-pushed the fix-ide-mixin branch 4 times, most recently from 8ded6fb to 3390d07 Compare March 21, 2019 19:10
This seems to match the behavior of Scala 2.13 and more importantly it
will be needed after the next commit that emits mixin forwarders as
bridges, otherwise `extends App` won't work.
This is the same scheme I proposed in
scala/scala#7843 which sidesteps all the issues
regarding mixin forwarders and generic signatures, see the discussion in
that PR for more information.

Tests imported from scalac, some of the comments in them might not be
correct for Dotty anymore.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants