Ben Sless

@ikitommi any interest in this patch? I can rebase it.

The same mechanism I used for the set could be used here - use a mutable java collection and expose it later by an immutable "view"

Creating an ArrayMap is tricky. You don't want to do it for over 8 keys, and createWithCheck will be worst-case quadratic for it.

```java static public PersistentArrayMap createWithCheck(Object[] init){ for(int i=0;i< init.length;i += 2) { for(int j=i+2;j

Ofc, you're right, the schema itself should be cached as well. The question then boils down to: Local cache per IntoSchema/schema instance, semi-global cache per context The context based solution...

First, you are correct regarding some of the methods I neglected. That was my oversight, I simply didn't read the bytecode fully, instead focusing on the constructor. With regards to...

Another thing to keep in mind which will be different in terms of bytecode and JVM representation is primitive classes (so records are defrecord- while primitive records will be --)...

see #53 and #55, possibly coming soon

Hi @Deraen, any update on this?

Hi @Deraen, been a while since we've both looked at it :) Coming back to the subject, I am not sure I see the rationale in working via a parser....