Unexpected compilation error with generic sealed interface

Vicente Romero vicente.romero at oracle.com
Mon Dec 28 16:41:36 UTC 2020


Hi,

I believe this to be the same issue already addressed in [1], which has 
already been fixed in 16 and should be forward-ported to 17,

Thanks,
Vicente

[1] https://bugs.openjdk.java.net/browse/JDK-8258662

On 12/28/20 5:33 AM, Mark Raynsford wrote:
> On 2020-12-27T23:40:50 +0100
> Remi Forax <forax at univ-mlv.fr> wrote:
>
>> Hi Mark,
>> this is an interesting snippet, while i struggle to understand why someone want to write a code like that, I is parametrized by T but the only possible subclass implements I<Object> so T is useless here,
>> anyway, the compiler should not reject that code so it's a bug.
> Hello!
>
> I think the original code was a collection of little functional data
> structures (Option, List, etc) to try out the combination of records
> and sealed classes.
>
> The code above is the result of removing things one by one until the
> result was a minimal example that would trigger the error.
>



More information about the amber-spec-experts mailing list