-
Notifications
You must be signed in to change notification settings - Fork 5
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
InterfaceOnly inheritance can lead to broken code #16
Comments
miho
added a commit
that referenced
this issue
Feb 6, 2019
miho
added a commit
that referenced
this issue
Feb 6, 2019
miho
added a commit
that referenced
this issue
Feb 6, 2019
- interface-only is equal to its read-only if effectively only getter-only properties have been specified. this allows immutable and mutable types to share getter-only & interface-only super-types - getter-only properties are correctly inherited by mutable types (previously, we required redeclaration of these properties)
miho
added a commit
that referenced
this issue
Feb 6, 2019
works now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To demonstrate the issue, let's look at the following model:
the code generator seems to ignore the fact that
ImmutableObj
extendsWithName
andMutableObj
inherits the@GetterOnly
annotation which leads to a missing setter method.The text was updated successfully, but these errors were encountered: