----- Original Message ----- > From: "naoto sato" <[email protected]> > To: "Archie L. Cobbs" <[email protected]>, "core-libs-dev" > <[email protected]>, "i18n-dev" <[email protected]> > Sent: Wednesday, September 9, 2026 10:16:26 PM > Subject: Re: RFR: 8391789: Collector for ListFormat
> On 9/9/26 12:18 PM, Anthony Vanelverdinghe wrote: >> Why would `Collectors.joining(listFormat)` conflict with the overload that >> takes >> `CharSequence`? Is this merely about the fact that `Collectors.joining(null)` >> would become ambiguous or am I missing something? > Yes, that ambiguity is the issue I was referring to. Unlikely, but > Collectors.joining(null) won't compile with that ambiguity. Hello, Usually, ambiguities are bad, but in this particular case, it's a good one. Collectors.joining(null) currently compiles and then fails at runtime. If Collectors.joining(listFormat) is added, Collectors.joining(null) will stop to compile, so a runtime error will be now detected at compile time. So it's a good ambiguity. > > Naoto regards, Rémi
