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
Move Scalac backend fork to lampepfl #1520
Comments
@felixmulder, what does this task mean? |
please summarize the discussion here once things clear up, i'd like to be in the loop on this one, understand what is meant. |
I think the idea is that we see little value maintaining the scalac backend (1) we are still tied to a snapshot of the scalac backend, instead of It seems more straightforward to just directly link to a version of the That's my tentative summary from talking to some of the people here. Quite Cheers
On Fri, Sep 16, 2016 at 9:04 PM, Lukas Rytz notifications@github.com
Prof. Martin Odersky |
Do you mean to copy the source into the dotty compiler? I think the original idea was to merge the backend abstraction layer into the Scala compiler, there was an attempt, but that didn't get very far (scala/scala#4136). The work to get that in would have to come from dotty's side. There is likely some value in keeping the same backend for the two compilers (there will be in the future). But if you're hitting a wall with the current solution it might make sense to go the other way. |
On Fri, Sep 16, 2016 at 10:01 PM, Lukas Rytz notifications@github.com
Yes, that's the crux of the matter. There's nobody willing to sign up to do
Prof. Martin Odersky |
It has been decided to keep the 2.11 backend fork from @DarkDimius, but to move it into the lampepfl organization |
Moved to http://github.com/lampepfl/scala/ |
No description provided.
The text was updated successfully, but these errors were encountered: