Skip to content
This repository was archived by the owner on Mar 26, 2020. It is now read-only.
This repository was archived by the owner on Mar 26, 2020. It is now read-only.

Java nullable annotation doesn't compile when applied to fully qualified names #397

@msjarrett

Description

@msjarrett

--java-nullable-annotation org.checkerframework.checker.nullness.qual.Nullable

If an interface uses a type from a different Java package (using @extern foo.yaml), the output will be @annotation fully.qualified.ClassName, which causes Java compilation problems.

For example:
public abstract io.grpc.Status send(Id recipient, @nullable com.google.package.Message message);

Results in:
error: scoping construct cannot be annotated with type-use annotation: @org.checkerframework.checker.nullness.qual.Nullable

Not a Java expert, but I think the correct way to apply the annotation is:
com.google.package.@nullable Message

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions