David P. Baker

We're just doing it.

Closing for now. We can always revisit.

@dependabot rebase

That should work. Which nullness analyzer are you using? What error are you seeing?

Can you summarize what the impact of this would be? What would that let people do that they can't do without it? If we don't accept this PR before 1.0,...

I see. That is a feature of [how type-use annotations are applied](https://www.oracle.com/technical-resources/articles/java/ma14-architect-annotations.html#:~:text=Applying%20Type%20Annotations). If you don't want to import, you can instead do this: ```java com.mypackage.@Nullable AEnum map(AnotherEnum anotherEnum) { ......

To clarify this issue, it proposes that we allow annotations that can target `FIELD`, `METHOD`, or `PARAMETER`, but not `TYPE_USE`, to imply a type-use annotation such as `@Nullable`. (If we...

**Current decision**: Because we are not planing to support annotation implication in 1.0 (#35, #307), this issue is not relevant for 1.0. **Proposal for 1.0: Finalize the current decision.** If...

**Decision**: This is related to a feature that will not be part of 1.0. It can remain open.

Hi @Ayush-Thakur-geek. Thanks for your PR. A few high-level comments: 1. We haven't yet decided to support weak values in `Multimap`s at all (#6985), so a PR is premature at...