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

What happens when an @Duck procedure returns a type but that type can't be found? #183

Open
dwtj opened this issue Mar 27, 2017 · 0 comments
Milestone

Comments

@dwtj
Copy link
Collaborator

dwtj commented Mar 27, 2017

@paninij currently gives a compile error such as this:

A capsule core has a procedure whose return type cannot be ducked. Cannot duck type `MyMissingType` because it has TypeKind ERROR.

Then subsequent capsule generation is not performed. This is annoying for an @paninij developer. This type may be generated by some other annotation processor in this round or in a later round of processing. The developer may also have just made a typo. In the former case, we are reporting an error where there is none. In the latter case, we are very noisily and cryptically announcing a missing type; @paninij should not be doing this: the normal Java compiler checks should be doing this.

@dwtj dwtj added this to the v0.3 milestone Mar 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant