-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Migrate Declaration to newer property style, class-ify ClassDefinition #859
Conversation
// Returns the enumerator corresponding to the most-derived type of this | ||
// object. | ||
auto Tag() const -> Kind { return tag; } | ||
auto tag() const -> Kind { return tag_; } |
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.
Can we call this kind
instead? That's what I wanted to call these methods originally, if not for the name collision with the Kind
type.
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.
Done, #860 covers this but may as well reduce merge conflicts here.
auto alternatives() const -> llvm::ArrayRef<Alternative> { | ||
return alternatives_; |
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.
Should this have a mutable overload?
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.
My preference is to do a mutable overload on an as-needed basis. I expect one to be added, it just didn't need one as of yet, I assume because code wasn't implemented to need it.
No description provided.