Skip to content

Sip/trait parameters #428

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

Merged
merged 4 commits into from
Jun 19, 2015
Merged

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Jun 18, 2015

New SIP: Trait Parameters

@heathermiller
Copy link
Member

Would you like to allow comments on these 2 SIPs?

@odersky
Copy link
Contributor Author

odersky commented Jun 19, 2015

@heathermiller Yes, of course. We want to review them.

@heathermiller
Copy link
Member

Ok, sure thing. I'll pull this in now and I'll add comments in the front matter in a follow-up commit (discus: true is the toggle switch for comments)

heathermiller added a commit that referenced this pull request Jun 19, 2015
@heathermiller heathermiller merged commit 2aac910 into scala:master Jun 19, 2015
@adriaanm
Copy link
Contributor

We agreed in the meeting last week that this proposal is desirable, but it would be useful to discuss a few more details:

  • interaction with context bounds encoding (and enumerate other potential interactions)
  • scoping (e.g., is a trait parameter in scope for the self type?)
  • binary compatibility / api evolution guidelines: adding a trait parameter has an impact on all subclasses that's slightly different from adding an abstract member because of the restrictions in passing arguments around, so it would be good to discuss this common scenario
  • are all modifier combinations legal?

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

Successfully merging this pull request may close these issues.

3 participants