1
93%
master: 93%

Ran 09 Mar 2023 09:58PM UTC

Files 78

Run time 1s

Badge

Embed ▾

Committed 09 Mar 2023 09:58PM UTC coverage: 93.129% (+0.03%) from 93.101%

Job # #1075.1

Build Type

push

github-actions

Committed by

web-flow

Commit Message

JSpecify generics checks for conditional expressions (#739)

For a conditional expression _e_, the type parameter nullability annotations of the true-subpart and false-subpart should match the annotations required by _e_'s context.  E.g., if _e_ is the right-hand side of an assignment, the annotations should match those for the type parameters for the assignment's left-hand side:
```java
// this is fine
A<@Nullable String> t = condition? new A<@Nullable String> : new A<@Nullable String>();
// this is bad
A<@Nullable String> t2 = condition? new A<String> : new A<String>();
// this is also bad
A<@Nullable String>  t1 = condition ? new A<String>(): new A<@Nullable String>()
```
Other contexts include returns, parameter passing, and being nested inside another conditional expression.  In our experience, it seems that `javac` captures the type parameter nullability required by _e_'s context in the type of _e_ itself.  So, our handling of conditional expressions simply checks that the types of both the true and false sub-expressions of _e_ are assignable to (i.e., a subtype of) the type of _e_, using the same machinery for checking assignments from #715.

Coverage Stats

5476 of 5880 relevant lines covered (93.13%)

0.93 hits per line

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

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job #1075.1

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

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job #1075.1

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

README BADGES
x