odenix

@semistone Are you using https://github.com/apple/pkl-spring or plain Pkl?

> It seems cleaner to me to end up with a single CLI parameter and property, that picks the flavor Can you clarify what you’re proposing here?

Not supporting `@Nullable`/`@NullMarked` means not supporting the recommended way to use jspecify. I’ve yet to see a project that uses jspecify and doesn’t use `@Nullable`/`@NullMarked`. If you think a generic...

> I don't think this needs to be deprecated; tools like IntelliJ let you configure nullability annotations. The intention here is that, by default, Pkl's generated code does not require...

I can barely read them. 

I have a PR ready. I'll send it once fewer PRs are in flight.

If the wins are minimal, I'm not sure they are worth the additional code and runtime checks. For typed objects, `cachedValues` could probably be removed altogether by switching to Truffle's...

How do you do your memory profiling? `members` is often shared between objects created by the same new/amend expression. Are specific code constructs, such as for-generators, responsible for what you're...

Owning the collection library(s) used by a Truffle language implementation makes a lot of sense: - it is desirable for performance reasons (can optimize for partial evaluation, etc.) - it...

I just stumbled upon the following conversation in the GraalVM Slack, where a Truffle committer argues for owning the collection library used in the Pkl interpreter. He's talking about Paguro,...