Inline deconstructing returned records would be a really sick feature.

@nipafx

2 жыл бұрын

I think so, too! Let's hope the Project Amber folks deem it worthy! 🤞🏾

It appears the current proposal uses positional destructuring, much the same way that method and constructor argument lists are positional, which is a bit of a shame. This greatly limits the usefulness of destructuring objects into its constituent parts. No one in their right mind would destructure a record of more than 3 fields if it requires declaring each and every field even when you don't care about some of them. There's also the issue of destructuring records à la "record SomeObject(String a, String b) {}". When, for whatever reason, someone decides to shift the declarations around, there's nothing except your testsuite to warn you that you've broken something somewhere in your codebase. Even the Kotlin language architects came out and admitted that positional destructuring was a mistake they made and that they should have opted for structural composition. While I have some reservations about the proposal as presented, I do feel there is merit to it. Granted, for small, localized, unambiguous records. Apologies for the rant...

Very informative update. Thanks for publishing!

Thanks mate. Very helpful.

wow! can't wait for destructing records in java

@tanveerhasan2382

2 жыл бұрын

Soon, brother

I hope that single underscore as a variable name will be re-introduced with a similar semantics that "blank identifier" in GO has.

Damn this makes nested processing of data much easier 👍

Can you please post a working example to illustrate the scenario of deconstructing records in pattern matching for learning purposes

Would be great to also instanceof check components like OrderEvent(_, VipOrder v) ; OrderEvent(_, Order usualOrder)

@nipafx

2 жыл бұрын

If `VipOrder extends/implements Order` (i.e. `Order` is no record) that would absolutely work. 👍

@askarkalykov

2 жыл бұрын

@@nipafx that's great! 😃 👍 I really like the direction Java is heading to, thank you and all the devs who are involved into making Java even more sexy and practical 👍👍👍

before destructorisation in Java: JS !== Java, and after JS != Java :P

Javaaaaaaa!!!

Hello Scala

Java going towards Javascript with its destruction

If you want to know why there is a shortage of hair gel product in the world just watch this video.

LOL all this is Scala stuff. All these JDK iterations are basically Java stealing Scala features one by one.