(Sorry if this is filed somewhere already)
It's come up a couple times now where we have generated code that creates struct-like classes with public fields. The NullAway default for unannotated code is to treat public fields as non-null, which removes warnings for field reads, but not for field writes. It would be great if fields of of unannotated classes would be considered @Nullable in the context of field writes.
In the particular case I'm working, I can update our code generator to annotate the fields, but thought I'd file this anyways.
(Sorry if this is filed somewhere already)
It's come up a couple times now where we have generated code that creates struct-like classes with public fields. The NullAway default for unannotated code is to treat public fields as non-null, which removes warnings for field reads, but not for field writes. It would be great if fields of of unannotated classes would be considered
@Nullablein the context of field writes.In the particular case I'm working, I can update our code generator to annotate the fields, but thought I'd file this anyways.