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.

Sign up for GitHub

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

Jump to bottom

Try to move dealiasing from Uncurry to Erasure info transform #297

Closed
retronym opened this issue Feb 4, 2017 · 2 comments
Closed

Try to move dealiasing from Uncurry to Erasure info transform #297

retronym opened this issue Feb 4, 2017 · 2 comments
Assignees
@retronym

Comments

@retronym
Copy link
Member

retronym commented Feb 4, 2017

No description provided.

@retronym retronym self-assigned this Feb 4, 2017
@retronym retronym added this to the 2.12.x milestone Feb 4, 2017
@retronym
Copy link
Member Author

retronym commented Feb 20, 2017 •
edited
Loading

Seems feasible, see the first commit of https://github.com/scala/scala/compare/2.12.x...retronym:topic/uncurry-without-dealias?expand=1

retronym added a commit to retronym/scala that referenced this issue Feb 20, 2017
@retronym
Move dealiasing from Uncurry to Erasure
034642e 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
@retronym retronym mentioned this issue Feb 20, 2017
Closed
retronym added a commit to retronym/scala that referenced this issue Feb 20, 2017
@retronym
Move dealiasing from Uncurry to Erasure
b00065f 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
retronym added a commit to retronym/scala that referenced this issue Feb 21, 2017
@retronym
Move dealiasing from Uncurry to Erasure
c41bbc5 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
retronym added a commit to retronym/scala that referenced this issue Mar 9, 2017
@retronym
Move dealiasing from Uncurry to Erasure
95be7ec 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
retronym added a commit to retronym/scala that referenced this issue Mar 14, 2017
@retronym
Move dealiasing from Uncurry to Erasure
9d9e255 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
retronym added a commit to retronym/scala that referenced this issue Mar 14, 2017
@retronym
Move dealiasing from Uncurry to Erasure
97ecfc9 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
retronym added a commit to retronym/scala that referenced this issue Mar 15, 2017
@retronym
Move dealiasing from Uncurry to Erasure
f774a88 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
retronym added a commit to retronym/scala that referenced this issue Mar 15, 2017
@retronym
Move dealiasing from Uncurry to Erasure
8406ad1 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
retronym added a commit to retronym/scala that referenced this issue Mar 15, 2017
@retronym
Move dealiasing from Uncurry to Erasure
3a65c3c 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
retronym added a commit to retronym/scala that referenced this issue Mar 15, 2017
@retronym
Move dealiasing from Uncurry to Erasure
3d56d7a 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
retronym added a commit to retronym/scala that referenced this issue Mar 19, 2017
@retronym
Move dealiasing from Uncurry to Erasure
ad7143b 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
retronym added a commit to retronym/scala that referenced this issue Mar 20, 2017
@retronym
Move dealiasing from Uncurry to Erasure
b24cf13 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
retronym added a commit to retronym/scala that referenced this issue Aug 20, 2017
@retronym
Move dealiasing from Uncurry to Erasure
ccbacdd 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
retronym added a commit to retronym/scala that referenced this issue Aug 24, 2017
@retronym
Move dealiasing from Uncurry to Erasure
8a3f2cf 
The motivation is to make the uncurry info tranform an identity
for more method signatures.

A few spots in erasure needed to be updated to account for
the possibility of aliases, by callng normalize and/or using
baseType rather than just assuming that the type args and class
type params line up.

Fixes scala/scala-dev#297
@adriaanm adriaanm modified the milestones: 2.12.x, 2.13.0-RC1 Sep 18, 2018
@SethTisue SethTisue modified the milestones: 2.13.0-RC1, 2.13.1 Feb 15, 2019
@szeiger szeiger modified the milestones: 2.13.1, 2.13.2 Sep 9, 2019
@SethTisue SethTisue modified the milestones: 2.13.2, 2.13.3 Feb 6, 2020
@SethTisue SethTisue modified the milestones: 2.13.3, 2.13.4 May 15, 2020
@dwijnand
Copy link
Member

You did try, it was a can of worms: scala/scala#5722 (comment)

@dwijnand dwijnand removed this from the 2.13.4 milestone Oct 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@retronym retronym

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@szeiger @retronym @adriaanm @SethTisue @dwijnand