On Tue, 16 Jun 2026 07:37:15 GMT, Jaikiran Pai <[email protected]> wrote:
>> Did you look at the generated javadoc? The generated javadoc will have the >> "PREVIEW" superscript after "value class" and would be interesting to see if >> that helps. >> >> (As it happens, I was discussed with Chen yesterday some further conditions >> that need to be listed here and whether they need additional clarification >> that they are a preview thing. The downside of more "Preview features is" or >> "When preview features are ..." is that it adds a lot of clutter to the >> list.) > >> Did you look at the generated javadoc? The generated javadoc will have the >> "PREVIEW" superscript after "value class" and would be interesting to see if >> that helps. > > I hadn't looked at the generated javadoc and wasn't aware that it generated > such a thing. I have been using webrev for the reviews and will check out the > rendered javadocs shortly and see if that's enough of an hint for such > specification updates. > The downside of more "Preview features is" or "When preview features are ..." > is that it adds a lot of clutter to the list.) I agree. Clutter which would have to be cleaned up afresh when the preview feature goes final. So yes, if there's a way to avoid this repeatition and still have some level of clarity in the specification updates that certain parts apply only for preview features, I think it's good to skip the "if/when preview features is enabled..." part. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/31123#discussion_r3418930873
