Viewing profile — joe_mwangi

Yeaaah. They are going to introduce approaches for the programmer to decide if tearability is allowed or not. Already there are internal annotations for fields and types to enable …

They are researching to have immutable arrays. Also multifields (stack allocated arrays as fields in value classes). So, there is a possibility.

I've done some tests with current value classes in latest prototype with full optimisation through annotation. Apparently, everything was being compiled to assembly code with no gc…

Also, this will be used for future null-restricted types.

Better late than never.

This time, 30mb.

Yup. By design, value classes will use cpu registers as a 1st priority instead.

Until they implement member patterns. https://openjdk.org/projects/amber/design-notes/patterns/tow...

> yet But up the comment section, someone thinks they won't be there 'in the future'

And I notice, people aren't aware more things are being planned for. For example, the carrier classes being proposed, they will separate state description with state representation…

And the only syntax change is adding 'value'.

Since they plan to have null-restricted types, then I don't see any issue.

But with null-restricted types, Integer! and int has no difference semantically and representation. They plan to introduce null-restricted types in future.

This is awesome. First step to an interesting direction of the language.

More reasons why java value classes will be a game changer.

Java’s planned approach is more like typeclass-style interfaces than unrestricted operator overloading. Types opt into core-defined operator contracts, rather than every library in…

Damn. You're old school. Java’s answer is virtual threads, not async/await. The idea is that most server-side IO can stay in direct style enabling blocking-looking code, cheap virt…

Notice you point out features that were easy to add during the beginning where there was no concern of backward compatibility? Now that java is porting value classes to mainline an…

Value types will be optionally null. What java will introduce to the tooling is narrowing of nullness types. Hence Foo! <: Foo? <: Foo. This will assist in enabling safe domains or…

Great stuff!!!

Yup. They started transferring to the main line, but will require many tests to know if they have any issues. https://github.com/openjdk/jdk/pull/31120

I'm actually planning to resurrect a dead raytracer project ( https://github.com/mambastudio/MambaTracer ) that has a GPU backend. And possible develop a future 2D API (a lot of wo…

It's a long roadmap, but this is their ultimate objective. Once java has value classes, future carrier classes and member patterns, that's when we shall see some very huge interest…

I have not used SBE but looking at it, my understanding is that it starts from an explicit schema, typically XML, and generates encoder/decoder flyweights over a binary buffer. Tha…

Interesting approach. I think Project Babylon did the same thing https://github.com/openjdk/babylon/blob/code-reflection/hat/... I had tested it and it's quite fast. Actually, you …