Sounds like a good idea. In my experience having @Nullable for returns is a good thing, as it quickly let a user of the API to see what's the contract.
Cos On Sun, Feb 08, 2015 at 04:36PM, Dmitriy Setrakyan wrote: > Hi Igniters, > > I want to revisit the use of the @Nullable annotation within the project. > What I am noticing more and more, is that @Nullable annotation just causes > extra warnings in IDE, especially on public API, causing most of the users > and developers to disable it. > > I want to propose the following policy: > - Use @Nullable for method parameters on public API for documentation > purposes. > - Do not use @Nullable for return types on public API to avoid unnecessary > warnings. > - Do not use @Nullable within internal implementation logic to avoid > unnecessary clutter in code. > > Thoughts? > > D.
