Re: RFR: JDK-8280168 Add Objects.toDefaultString [v2]

2022-01-19 Thread Mandy Chung
On Wed, 19 Jan 2022 02:57:10 GMT, Joe Darcy wrote: >> While it is strongly recommend to not use the default toString for a class, >> at times it is the least-bad alternative. When that alternative needs to be >> used, it would be helpful to have the implementation already available, such >> as

Re: RFR: JDK-8280168 Add Objects.toDefaultString [v2]

2022-01-19 Thread Alan Bateman
On Wed, 19 Jan 2022 02:57:10 GMT, Joe Darcy wrote: >> While it is strongly recommend to not use the default toString for a class, >> at times it is the least-bad alternative. When that alternative needs to be >> used, it would be helpful to have the implementation already available, such >> as

Re: RFR: JDK-8280168 Add Objects.toDefaultString [v2]

2022-01-18 Thread Joe Darcy
On Wed, 19 Jan 2022 02:22:33 GMT, Roger Riggs wrote: >> Joe Darcy has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Respond to review feedback. > > src/java.base/share/classes/java/util/Objects.java line 170: > >> 168: * {@return a s

Re: RFR: JDK-8280168 Add Objects.toDefaultString [v2]

2022-01-18 Thread Joe Darcy
> While it is strongly recommend to not use the default toString for a class, > at times it is the least-bad alternative. When that alternative needs to be > used, it would be helpful to have the implementation already available, such > as in Objects.toDefaultString(). This method is analagous t