Re: RFR: JDK-8285939: javadoc java.lang.Record should not have "Direct Known Subclasses:" section [v3]

2022-05-31 Thread Jonathan Gibbons
On Mon, 30 May 2022 15:16:07 GMT, Pavel Rappo wrote: >> Jonathan Gibbons has updated the pull request with a new target base due to >> a merge or a rebase. The pull request now contains five commits: >> >> - Merge remote-tracking branch 'upstream/master' into >> 8285939.record-subtypes >> -

Re: RFR: JDK-8285939: javadoc java.lang.Record should not have "Direct Known Subclasses:" section [v3]

2022-05-31 Thread Jonathan Gibbons
On Mon, 30 May 2022 14:06:54 GMT, Pavel Rappo wrote: >> Jonathan Gibbons has updated the pull request with a new target base due to >> a merge or a rebase. The pull request now contains five commits: >> >> - Merge remote-tracking branch 'upstream/master' into >> 8285939.record-subtypes >> -

Re: RFR: JDK-8285939: javadoc java.lang.Record should not have "Direct Known Subclasses:" section [v3]

2022-05-31 Thread Jonathan Gibbons
On Mon, 30 May 2022 13:41:33 GMT, Pavel Rappo wrote: >> Jonathan Gibbons has updated the pull request with a new target base due to >> a merge or a rebase. The pull request now contains five commits: >> >> - Merge remote-tracking branch 'upstream/master' into >> 8285939.record-subtypes >> -

Re: RFR: JDK-8285939: javadoc java.lang.Record should not have "Direct Known Subclasses:" section [v3]

2022-05-30 Thread Pavel Rappo
On Wed, 25 May 2022 20:55:21 GMT, Jonathan Gibbons wrote: >> As described in the JBS issue, the observed problem is a side-effect of a >> related but different issue, which is that record classes are not treated >> the same was as enum classes when it comes to generating the class hierarchy

Re: RFR: JDK-8285939: javadoc java.lang.Record should not have "Direct Known Subclasses:" section [v3]

2022-05-25 Thread Jonathan Gibbons
> As described in the JBS issue, the observed problem is a side-effect of a > related but different issue, which is that record classes are not treated the > same was as enum classes when it comes to generating the class hierarchy in > `ClassTree`. Because record classes are not treated