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

SIP for supporting named type arguments and partial type argument lists #456

Closed
wants to merge 4 commits into
base: master
from

Conversation

Projects
None yet
6 participants
@ahmadsalim

ahmadsalim commented Sep 12, 2015

This follows directly from the discussion in scala-debate and other relevant discussion mentioned in the SIP.

All comments are welcome.

@dickwall

This comment has been minimized.

Show comment
Hide comment
@dickwall

dickwall Nov 16, 2015

Contributor

Please fix the formatting for the code examples. This will be reviewed again in the December SLIP meeting.

Contributor

dickwall commented Nov 16, 2015

Please fix the formatting for the code examples. This will be reviewed again in the December SLIP meeting.

@SethTisue

This comment has been minimized.

Show comment
Hide comment
@SethTisue

SethTisue Nov 16, 2015

Member

sorry for the delay @ahmadsalim, we inadvertently lost this in the shuffle

Member

SethTisue commented Nov 16, 2015

sorry for the delay @ahmadsalim, we inadvertently lost this in the shuffle

@ahmadsalim

This comment has been minimized.

Show comment
Hide comment
@ahmadsalim

ahmadsalim Nov 16, 2015

Thanks! I will fix the formatting

ahmadsalim commented Nov 16, 2015

Thanks! I will fix the formatting

Fixes code formatting for proposal
I changed from the Jekyll-based `{%highlight%}` directives to standard Markdown code blocks.
@SethTisue

This comment has been minimized.

Show comment
Hide comment
@SethTisue

SethTisue Dec 14, 2015

Member

sorry, we ended up having to canceling the December SIP/SLIP meeting where this would have been discussed — we will reschedule for January.

Member

SethTisue commented Dec 14, 2015

sorry, we ended up having to canceling the December SIP/SLIP meeting where this would have been discussed — we will reschedule for January.

@ahmadsalim

This comment has been minimized.

Show comment
Hide comment
@ahmadsalim

ahmadsalim Dec 14, 2015

Sure, I will look forward to hear your response.

ahmadsalim commented Dec 14, 2015

Sure, I will look forward to hear your response.

@SethTisue

This comment has been minimized.

Show comment
Hide comment
@SethTisue

SethTisue Jan 11, 2016

Member

we discussed this at the SLIP/SIP meeting today, video link https://www.youtube.com/watch?v=Kp4Ev-2xjWU. full notes from the meeting aren't up yet, but I would summarize as follows: all are sympathetic, but the proposal as its stands is not sufficiently detailed to qualify as a SIP yet. there is speculative work on named type parameters happening in a Dotty context, with the motivation going beyond just supporting partial type application; that's the likeliest path forward for something in this space, so we suggest engaging the Dotty team on it.

Member

SethTisue commented Jan 11, 2016

we discussed this at the SLIP/SIP meeting today, video link https://www.youtube.com/watch?v=Kp4Ev-2xjWU. full notes from the meeting aren't up yet, but I would summarize as follows: all are sympathetic, but the proposal as its stands is not sufficiently detailed to qualify as a SIP yet. there is speculative work on named type parameters happening in a Dotty context, with the motivation going beyond just supporting partial type application; that's the likeliest path forward for something in this space, so we suggest engaging the Dotty team on it.

@SethTisue

This comment has been minimized.

Show comment
Hide comment
Member

SethTisue commented Jan 12, 2016

@ahmadsalim

This comment has been minimized.

Show comment
Hide comment
@ahmadsalim

ahmadsalim Jan 12, 2016

@SethTisue Thank you and the committee for taking time to discuss my proposal, I can certainly see your points that there are issues there that needs to be fleshed out. I will try to contact the dotty team soon and see what further development there is needed.

ahmadsalim commented Jan 12, 2016

@SethTisue Thank you and the committee for taking time to discuss my proposal, I can certainly see your points that there are issues there that needs to be fleshed out. I will try to contact the dotty team soon and see what further development there is needed.

@jvican

This comment has been minimized.

Show comment
Hide comment
@jvican

jvican Sep 23, 2016

Member

Hi @ahmadsalim! Is there any news or progress on this?

Member

jvican commented Sep 23, 2016

Hi @ahmadsalim! Is there any news or progress on this?

@ahmadsalim

This comment has been minimized.

Show comment
Hide comment
@ahmadsalim

ahmadsalim Sep 25, 2016

@jvican Hi.

So as far as I understand my SIP draft was nowhere near complete to be converted to an official SIP. At the SLIP meeting, the responsible actors stated that they were currently developing something overlapping in the dotty team, and suggested I should contact them to coordinate.

I wrote an e-mail to the dotty developers mailing list around that time (January), but I unfortunately did not get any response back then (and thus moved on to doing other things more relevant to my work). I would however still assume that the Dotty team has something under development with regards to this aspect, and so I would try to contact them about the state of affairs if you are interested in this features.

In any case, thank you for the interest. I will close the PR now, which I long had forgotten to do.

ahmadsalim commented Sep 25, 2016

@jvican Hi.

So as far as I understand my SIP draft was nowhere near complete to be converted to an official SIP. At the SLIP meeting, the responsible actors stated that they were currently developing something overlapping in the dotty team, and suggested I should contact them to coordinate.

I wrote an e-mail to the dotty developers mailing list around that time (January), but I unfortunately did not get any response back then (and thus moved on to doing other things more relevant to my work). I would however still assume that the Dotty team has something under development with regards to this aspect, and so I would try to contact them about the state of affairs if you are interested in this features.

In any case, thank you for the interest. I will close the PR now, which I long had forgotten to do.

@ahmadsalim ahmadsalim closed this Sep 25, 2016

@jvican

This comment has been minimized.

Show comment
Hide comment
@jvican

jvican Sep 25, 2016

Member

Hi @ahmadsalim, I suggest you to contact @smarter, @felixmulder or @DarkDimius for more information on the dotty side. Hope that you reopen this soon. Thanks to you!

Member

jvican commented Sep 25, 2016

Hi @ahmadsalim, I suggest you to contact @smarter, @felixmulder or @DarkDimius for more information on the dotty side. Hope that you reopen this soon. Thanks to you!

@felixmulder

This comment has been minimized.

Show comment
Hide comment
@felixmulder

felixmulder Sep 27, 2016

Contributor

This was at one point implemented in Dotty, but it was removed because of performance issues with the implementation. @DarkDimius knows more.

Cheers,
Felix

Contributor

felixmulder commented Sep 27, 2016

This was at one point implemented in Dotty, but it was removed because of performance issues with the implementation. @DarkDimius knows more.

Cheers,
Felix

@ahmadsalim

This comment has been minimized.

Show comment
Hide comment
@ahmadsalim

ahmadsalim Sep 27, 2016

@jvican @felixmulder Ah great, thanks for the update!

ahmadsalim commented Sep 27, 2016

@jvican @felixmulder Ah great, thanks for the update!

@Blaisorblade

This comment has been minimized.

Show comment
Hide comment
@Blaisorblade

Blaisorblade May 13, 2018

Contributor

Fixed in Dotty 0.8.0-RC1 (EDIT: quite a bit before I assume, but I tested that version):

scala> def f[A, B](x: A, y: B) = x
def f[A, B](x: A, y: B): A
scala> f[A = Int](_, "")
val res2: Int => Int = Lambda$1344/204568533@76f856a8
Contributor

Blaisorblade commented May 13, 2018

Fixed in Dotty 0.8.0-RC1 (EDIT: quite a bit before I assume, but I tested that version):

scala> def f[A, B](x: A, y: B) = x
def f[A, B](x: A, y: B): A
scala> f[A = Int](_, "")
val res2: Int => Int = Lambda$1344/204568533@76f856a8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment