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

Complete the messages. #3

Merged
merged 1 commit into from
Jul 27, 2019

Conversation

xingweitian
Copy link
Contributor

No description provided.

subclass.bound.incompatible
method.receiver.incompatible=Incompatible method receiver: %s
class.bound.invalid=Invalid class bound: %s
subclass.bound.incompatible=Incompatible subclass bound: %s
Copy link
Member

Choose a reason for hiding this comment

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

When is this error raised? Should the message be similar to super.constructor.invocation.incompatible, something like Subclass bound %s is not compatible with super class bound %s?
In general I find the term "subclass" strange and we should look to clean this terminology up.
But let's do both of these improvements in separate PRs.

@wmdietl wmdietl merged commit 0ee8410 into opprop:adapt-to-cf-master Jul 27, 2019
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.

2 participants