-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Remainder of the Spec updates about removals #16841
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
Conversation
As Scala 2 macros were an experimental feature, they were not included in the spec, and the macro keyword is still a keyword there is thus nothing to do (Scala 3 macros will get their own commits through the corresponding pages)
Scala 3 does not infer more precise types for the return type of overriding methods. This can be seen in the following example: ```scala type T type U <: T abstract class A{ def m: T } class B extends A{ def m = ??? : U } val res: U = (new B).m ```
As the feature is not actually deprecated, no changes to the spec are needed
Will make it easier to explain later what happens when you apply a using method to explicit parameters
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed this PR commit by commit and commented on what needs to be done before we can merge it.
effort to approximate existential types with its own types. It will | ||
issue a warning that a precise emulation is not possible. | ||
|
||
### Procedure Syntax |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that section should be dropped from the spec, IMHO it belongs to the migration guide.
@julienrf Did you intentionally push the "Wildcard Types" commit to this PR branch? |
Yes, I wanted to shape this PR to a mergeable state. |
I believe this ready for merging now. @julienrf do you agree? |
Specify them independently of `forSome`.
This is the rest of the work I did on the Spec, it is not in individual PRs, but still follows the other principles outlined in #16839 and in
docs/_spec/README.md