eirikbakke commented on PR #8799: URL: https://github.com/apache/netbeans/pull/8799#issuecomment-3272590298
> The deprecation and javadoc notes on [value objects](https://docs.oracle.com/en/java/javase/24/docs/api/java.base/java/lang/doc-files/ValueBased.html#Value-basedClasses) describe what applications should do to be future proof. That's good for new code, but for existing APIs, perhaps it's better to just leave them as-is? I'd be surprised if JDK changes behavior in a way that is likely to break client applications. (The example they give of a possible future change is that "synchronization may fail", but that would be a much more obscure use of an Integer instance.) -- 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: notifications-unsubscr...@netbeans.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org For additional commands, e-mail: notifications-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
