theigl commented on PR #1093: URL: https://github.com/apache/wicket/pull/1093#issuecomment-2640040773
> > I'll wait for what the final decision will be: Jakarta or JSpecify. > > For me both are meh. > > * The annotations will add a lot of noise > * The changes will make cherry-picking harder, unless someone volunteers to backport them to 9.x too Yeah, both of these concerns are valid. In my experience, when a whole package is marked as `@NullMarked` and only `@Nullable` is used, the noise is limited and the safety gained from it is worth it (and no more unnecessary if-not-null-checks). Also when new code or files are added to the package, the IDE will automatically show warnings if new code is not null-marked correctly. I'm also unsure about proceeding with this if we don't have a concrete and unseful final result in mind. -- 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]
