4 ms·
https://www.jetbrains.com/help/idea/annotating-source-code.html#disable-nullability-assertions https://www.jetbrains.com/help/idea/annotating-source-code.h...
by rhdunn 1y ago
https://www.jetbrains.com/help/idea/annotating-source-code.html#disable-nullability-assertions https://www.jetbrains.com/help/idea/annotating-source-code.h...
> When you compile your project with IntelliJ IDEA build tool, the IDE adds assertions to all code elements annotated with @NotNull. These assertions will throw an error if the elements happen to be null at runtime.
- bingabingabinga 1y ago[dead]
- vbezhenar 1y agoThat's not java compiler. That's intellij compiler. I'd say that's very weird anti-feature, because your build in IDE and maven will work differently.
- wokkel 1y agoWhen using Lombok it will use a compiler plugin for this so maven builds have @nonnull generated as if-statements. I dont know if intellij uses their own plugin but they do support Lombok in maven projects, so maybe thats where this is coming from. Afaik intellij has no built in compiler but relies on java .
- Bjartr 1y agoLombok hijacks the compiler to do it's own thing, and violates the contract Java compiler plugins are supposed to follow. See this comment by an OpenJDK tech lead: https://news.ycombinator.com/item?id=37666793 https://news.ycombinator.com/item?id=37666793
- lisbbb 1y agoI was initially impressed with Lombok and then ran into all the downsides of it and it was institutionally abandoned at one particular firm I was with (100s of devs).