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.

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

Trees: use Term.ArgClause, not List[Term] #2942

Merged
merged 1 commit into from
Nov 10, 2022
Merged

Conversation

kitbellew
Copy link
Contributor

Helps with #2869.

Copy link
Collaborator

@tgodzik tgodzik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some smaller comments, otherwise LGTM

extends Term {
@replacedField("4.6.0") final def targs: List[Type] = targClause.values
@replacedField("4.6.0") final def args: List[Term] = argClause.values
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we deprecate the old fields so that users know that this changed?

checkFields(tpe.isConstructable)
checkParent(ParentChecks.Init)
@replacedField("4.6.0") final def argss: List[List[Term]] = argClauses.map(_.values).toList
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here with, let's show that users should not use the old methods with @ deprecated

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the replacedField annotation macro adds deprecation warning. i can double-check, though.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't seen them being deprecated when I checked locally released version 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you are right, of course. fixed in #2960.

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.

None yet

2 participants