Skip to content
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

Closed
felixmulder opened this issue Sep 16, 2016 · 8 comments
Closed

Move Scalac backend fork to lampepfl #1520

felixmulder opened this issue Sep 16, 2016 · 8 comments
Assignees

Comments

@felixmulder
Copy link
Contributor

No description provided.

@DarkDimius
Copy link
Member

@felixmulder, what does this task mean?

@felixmulder
Copy link
Contributor Author

Good question - I'd rather @smarter or @odersky explain this for fear of getting it wrong. Otherwise let's talk about it on Tuesday.

@lrytz
Copy link
Member

lrytz commented Sep 16, 2016

please summarize the discussion here once things clear up, i'd like to be in the loop on this one, understand what is meant.

@odersky
Copy link
Contributor

odersky commented Sep 16, 2016

I think the idea is that we see little value maintaining the scalac backend
bridge. Right now it looks to us that this bridge won't be maintained by
the Scala team. So this means that

(1) we are still tied to a snapshot of the scalac backend, instead of
being able to upgrade continuously
(2) only Dmitry knows how to do fixes for the backend
(3) Doing any fixes to the backend is needlessly complex in both
development and deployment.

It seems more straightforward to just directly link to a version of the
backend and merge scalac improvements into it as they come online.

That's my tentative summary from talking to some of the people here. Quite
happy to revise it if different arguments come up.

Cheers

  • Martin

On Fri, Sep 16, 2016 at 9:04 PM, Lukas Rytz notifications@github.com
wrote:

please summarize the discussion here once things clear up, i'd like to be
in the loop on this one, understand what is meant.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1520 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAwlVg9nPpGlf1HkQa0z-qm_DarwKOkXks5qquhAgaJpZM4J_FVp
.
{"api_version":"1.0","publisher":{"api_key":"
05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":
{"external_key":"github/lampepfl/dotty","title":"
lampepfl/dotty","subtitle":"GitHub repository","main_image_url":"
https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-
11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://
cloud.githubusercontent.com/assets/143418/15842166/
7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in
GitHub","url":"https://github.com/lampepfl/dotty"}},"
updates":{"snippets":[{"icon":"PERSON","message":"@lrytz in #1520: please
summarize the discussion here once things clear up, i'd like to be in the
loop on this one, understand what is meant."}],"action":{"name":"View
Issue","url":"https://github.com/lampepfl/dotty/issues/
1520#issuecomment-247681532"}}}

Prof. Martin Odersky
LAMP/IC, EPFL

@lrytz
Copy link
Member

lrytz commented Sep 16, 2016

directly link to a version of the backend

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.

@odersky
Copy link
Contributor

odersky commented Sep 17, 2016

On Fri, Sep 16, 2016 at 10:01 PM, Lukas Rytz notifications@github.com
wrote:

directly link to a version of the backend

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 scala/scala#4136). The work to
get that in would have to come from dotty's side.

Yes, that's the crux of the matter. There's nobody willing to sign up to do
this. Since we are a volunteering effort there's little we can do to change
this.

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 ways.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1520 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAwlVsKl3p706HsA1yANWgrQvtEi3BRGks5qqvW0gaJpZM4J_FVp
.
{"api_version":"1.0","publisher":{"api_key":"
05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":
{"external_key":"github/lampepfl/dotty","title":"
lampepfl/dotty","subtitle":"GitHub repository","main_image_url":"
https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-
11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://
cloud.githubusercontent.com/assets/143418/15842166/
7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in
GitHub","url":"https://github.com/lampepfl/dotty"}},"
updates":{"snippets":[{"icon":"PERSON","message":"@lrytz in #1520: \u003e
directly link to a version of the backend\r\n\r\nDo you mean to copy the
source into the dotty compiler?\r\n\r\nI 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 (https://github.com/scala/
/pull/4136). The work to get that in would have to come from dotty's
side.\r\n\r\nThere 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."}],"action":{"name":"View Issue","url":"https://github.
com//issues/1520#issuecomment-247694859"}}}

Prof. Martin Odersky
LAMP/IC, EPFL

@felixmulder
Copy link
Contributor Author

It has been decided to keep the 2.11 backend fork from @DarkDimius, but to move it into the lampepfl organization

@felixmulder felixmulder added this to the 0.1 Tech Preview milestone Apr 4, 2017
@felixmulder felixmulder changed the title Fork Scalac backend Move Scalac backend fork to lampepfl Apr 4, 2017
@felixmulder felixmulder self-assigned this Apr 4, 2017
@DarkDimius
Copy link
Member

Moved to http://github.com/lampepfl/scala/

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

No branches or pull requests

4 participants