Commit f3b9181
authored
Fix for explicitly-typed lambda parameters in JDK 24+ (uber#1452)
This case worked before JDK 24 since somehow our code that looked at the
owner of a symbol found the annotation; for some reason it stopped
working. Looking at annotations on the `type` field of the symbol seems
to find what we need.
Fixes uber#1448
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
## Bug Fixes
* Enhanced nullability annotation detection to recognize type-use
annotations on symbol types, improving coverage for explicitly-annotated
lambda parameters that were previously undetected.
## Tests
* Added test coverage for enhanced annotation detection in generic
lambda scenarios.
<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>
<!-- end of auto-generated comment: release notes by coderabbit.ai -->1 parent 1167221 commit f3b9181
File tree
2 files changed
+32
-0
lines changed- nullaway/src
- main/java/com/uber/nullaway
- test/java/com/uber/nullaway/jspecify
2 files changed
+32
-0
lines changedLines changed: 7 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
211 | 211 | | |
212 | 212 | | |
213 | 213 | | |
| 214 | + | |
| 215 | + | |
| 216 | + | |
| 217 | + | |
| 218 | + | |
| 219 | + | |
| 220 | + | |
214 | 221 | | |
215 | 222 | | |
216 | 223 | | |
| |||
Lines changed: 25 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
133 | 133 | | |
134 | 134 | | |
135 | 135 | | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
| 140 | + | |
| 141 | + | |
| 142 | + | |
| 143 | + | |
| 144 | + | |
| 145 | + | |
| 146 | + | |
| 147 | + | |
| 148 | + | |
| 149 | + | |
| 150 | + | |
| 151 | + | |
| 152 | + | |
| 153 | + | |
| 154 | + | |
| 155 | + | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
| 159 | + | |
| 160 | + | |
136 | 161 | | |
137 | 162 | | |
138 | 163 | | |
| |||
0 commit comments