We need the APIs to be consistent.
Any particular technical reason for this? Personally, I would be tempted to say "boolean" when it can't be null, and @Nullable Boolean otherwise, but that's just a somewhat context-free style preference.
ap
We need the APIs to be consistent.
Any particular technical reason for this? Personally, I would be tempted to say "boolean" when it can't be null, and @Nullable Boolean otherwise, but that's just a somewhat context-free style preference.
ap