theigl commented on PR #1093: URL: https://github.com/apache/wicket/pull/1093#issuecomment-2631750844
> If something isn't marked, it should be presumed to be 'nullable', since that is the language default. > IMO, less noise is better. Marking with `@Nullable` produces significantly less noise in my experience. While it is true that at the language level almost everything is nullable, in a typical project, the majority of values are never null. I recently annotated hundreds of thousands of LOC in my main project and I would have needed at least 3-5x the amount of annotations if I went with `@Nonnull`. But marking as `@Nullable` only makes sense together with a `@Nullmarked` or `@ParametersAreNonnullByDefault` annotation. Otherwise it doesn't provide much value. So if we stick with `jakarta.annotation` I think that only the current `@Nonnull` approach makes sense. @jstuyts: Are you consuming Wicket APIs from Kotlin? If so, does adding these `@Nonnull`s already help with null-safety in Kotlin? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
