David P. Baker

Curious: Why are we doing this as a standard PR rather than through Copybara?

`RateLimiter` doesn't have such a feature. Can you describe the use case that you think people will have in some more detail?

To be clear, is this request distinct from #1778?

It isn't, yet. This issue is still open.

**Current decision**: `@Nullable` and `@NonNull` are applicable to non-root type components of local variable declarations and cast expressions. **Argument for changing**: No strong case. **Timing**: This must be decided before...

I'm not sure I understand your first part. I don't see any argument for the nullness of non-root types in casts to be inferred or optional. Are you looking for...

**Current decision**: ~Type parameters whose upper bound is nullable have "parametric nullness", while those whose upper bound is non-null are simply non-null.~ [EDIT on 2024-06-14:] Unprojected type variables in null-marked...

@kevinb9n Is that rewording about changing the order of the cases, or about using the term "type variable" rather than "type parameter"? What about this? "Unprojected type variable usages in...

This issue is only about parametric nullness; we can discuss unspecified elsewhere. I've made an edit to the [proposal](https://github.com/jspecify/jspecify/issues/275#issuecomment-2045981298). Please take another look.

**Current decision**: Lambda parameters that are `var` or untyped have their nullness inferred. `@Nullable` and `@NonNull` apply to those with explicit types just like method parameters. **Argument for changing**: None....