Skip to content

Drop Type Projections #5374

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
Closed
odersky opened this issue Nov 2, 2018 · 5 comments
Closed

Drop Type Projections #5374

odersky opened this issue Nov 2, 2018 · 5 comments
Labels
area:documentation stat:needs spec

Comments

@odersky
Copy link
Contributor

odersky commented Nov 2, 2018

We need to clarify exactly what abstract types are illegal.
@odersky
Copy link
Contributor Author

odersky commented Nov 2, 2018

In fact, the spec says exactly what is implemented: T # A is an error is T is an abstract type, no matter what A is.

@odersky
Copy link
Contributor Author

odersky commented Nov 2, 2018

See #5375 for a test case.

@odersky odersky closed this as completed Nov 2, 2018
@odersky odersky reopened this Nov 3, 2018
@odersky
Copy link
Contributor Author

odersky commented Nov 3, 2018

The precise semantics is: In T # A, T must be realizable. Actually, this would be a good place to add a spec of realizability, which is currently missing.

@odersky odersky closed this as completed in c04eb15 Nov 4, 2018
@allanrenucci allanrenucci reopened this Nov 4, 2018
@LPTK LPTK mentioned this issue May 6, 2020
Closed
@Blaisorblade Blaisorblade removed their assignment Jul 1, 2020
@bblfish bblfish mentioned this issue Aug 24, 2020
Closed
@ckipp01
Copy link
Member

ckipp01 commented May 11, 2023

Hey @odersky is this still something needed or something you plan on doing? If not, is this something that can be closed? I also removed the SIP from the title just to avoid any confusion.

@ckipp01 ckipp01 changed the title SIP: Drop Type Projections Drop Type Projections May 11, 2023
@odersky
Copy link
Contributor Author

odersky commented May 11, 2023

As far as I am concerned this can be closed. Not sure anymore why it was re-opened.

@odersky odersky closed this as completed May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area:documentation stat:needs spec
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@smarter @Blaisorblade @odersky @allanrenucci @ckipp01