theigl commented on PR #1093: URL: https://github.com/apache/wicket/pull/1093#issuecomment-2633329667
> So it seems to me that JSpecify is not in a usable state yet. Is there a preference for one of the other supported annotations? I don't see a good candidate as most of them are part of a library that is not specifically meant to strengthen contracts, is vendor-specific or is (as good as) obsolete. JSpecify is perfectly usable already but it has a couple of non-intuitive annotation usages. Your example is one of them. See https://jspecify.dev/docs/user-guide/#some-subtler-details. You have to either use static imports or write it like this: ```WebResponse.@NonNull CacheScope scope``` Another example is with arrays. I always have to think twice where to put the annotation depending on if the array itself is nullable or its elements are. -- 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]
