1
93%
master: 93%

Ran 21 Jun 2022 10:35PM UTC

Files 75

Run time 99min

Badge

Embed ▾

Committed 21 Jun 2022 10:33PM UTC coverage: 92.538% (-0.04%) from 92.575%

Job # #881.1

Build Type

push

github-actions

Committed by

web-flow

Commit Message

Treat Void formal arguments as @Nullable (#613)

This is a follow up on #595. See that PR for some of the soundness
caveats related to method overriding and the nullability of Void
in our current implementation.

This does, however, avoid some otherwise awkward suppressions,
as shown in #608.

There are two correct ways of handling Void:

a) Having it default to `@Nullable` as a type, which requires us
   adding a "default nullability" for some types/classes and explicitly
   contradicts JSpecify (jspecify/jspecify#51)
b) Supporting generics, and requiring explicitly annotating `@Nullable Void`.
   This will probably also require third-party libraries which we consider
   annotated (such as CF), to adopt this convention.

I believe (b) is the way forward long-term, which means that, for now,
this hack might be the best we can do without generics support. Once
NullAway supports generics, both this change and #595 should be reverted.

Run Details

4824 of 5213 relevant lines covered (92.54%)

0.93 hits per line

uber / NullAway / #881 / 1
93%
master: 93%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job #881.1

uber / NullAway / #881 / 1 93% master: 93%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job #881.1

uber / NullAway / #881 / 1
93%
master: 93%

README BADGES
x