Skip to content

Swap order of arguments in annotations #969

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 2 commits into from
Nov 22, 2015

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Nov 22, 2015

The fact that the annotation comes first is weird, because when I write
an annotated type it's @. Also, annotated types
are like RefinedTypes in that they derive from a parent type. And in
RefinedTypes the parent comes first.

So swapping the arguments improves consistency. Review by @VladimirNik.
@VladimirNik can you take this PR over to do the same change in the TASTY format?

odersky and others added 2 commits November 22, 2015 18:03
The fact that the annotation comes first is weird, because when I write
an annotated type it's <type> @<annotation>. Also, annotated types
are like RefinedTypes in that they derive from a parent type. And in
RefinedTypes the parent comes first.

So swapping the arguments improves consistency.
@VladimirNik
Copy link
Contributor

I changed rule for Annotated pickling to:
ANNOTATED Length underlying_Type fullAnnotation_Term

@odersky Could you please modify it in TASTY Reference Manual? I haven't got write access to it.

@VladimirNik
Copy link
Contributor

LGTM

DarkDimius added a commit that referenced this pull request Nov 22, 2015
@DarkDimius DarkDimius merged commit 4463f5e into scala:master Nov 22, 2015
@allanrenucci allanrenucci deleted the change-swap-annot-args branch December 14, 2017 16:58
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.

4 participants