- Original Message -
> From: "Jochen Theodorou"
> To: "dev"
> Sent: Sunday, January 28, 2024 10:38:24 PM
> Subject: Re: [EXT] Re: ClassFile API
> On 28.01.24 15:05, Remi Forax wrote:
> [...]
>> Hello,
>> before i answer to your question
On 28.01.24 15:05, Remi Forax wrote:
[...]
Hello,
before i answer to your questions,
my remark about sealed types is that the API of the classfile library is based
on sealed types and pattern matching.
A sealed type is not extensible meaning that if you target a specific version
of the classfil
- Original Message -
> From: "Jochen Theodorou"
> To: "dev"
> Sent: Sunday, January 28, 2024 1:19:24 PM
> Subject: Re: [EXT] Re: ClassFile API
> On 27.01.24 18:58, Remi Forax wrote:
> [...]
>> The classfile API uses sealed types, once those w
On 27.01.24 18:58, Remi Forax wrote:
[...]
The classfile API uses sealed types, once those will be updated either the
groovy compiler will need to be updated or a default of a switch will be called.
See how the overview of the API uses "default" everywhere.
https://cr.openjdk.org/~asotona/JD
- Original Message -
> From: "Jochen Theodorou"
> To: "dev"
> Sent: Saturday, January 27, 2024 12:35:40 PM
> Subject: Re: [EXT] Re: ClassFile API
> On 23.01.24 19:33, Milles, Eric (TR Technology) via dev wrote:
>> An API like this works fine f
On 23.01.24 19:33, Milles, Eric (TR Technology) via dev wrote:
An API like this works fine for straightline code. But if you need to add
instructions conditionally, repeat blocks for additional instances, or other
complex scenarios; builders can quickly break down. I would wait to see how
th
An API like this works fine for straightline code. But if you need to add
instructions conditionally, repeat blocks for additional instances, or other
complex scenarios; builders can quickly break down. I would wait to see how
the class file api shakes out before turning over nearly all of cla
