Java 22 Previews Statements Before `super(...)` and `this(...)` - Inside Java Newscast #62
Вставка
- Опубліковано 8 чер 2024
- Whether for validation, preparation, or splitting and sharing arguments, it can be quite annoying that Java doesn't allow statements before the `super(...)` or `this(...)` call in a constructor. Luckily Java 22 is about to change that with JEP 447, which previews statements before the explicit constructor invocation.
JEP 447: openjdk.org/jeps/447
JDK 22: jdk.java.net/22/
~~~ Chapters ~~~
0:00 Intro
1:40 Constructor Chaining
2:57 No Statements Before Constructor Invocation
5:04 JEP 447
6:40 Prologue Benefits
7:46 COWS!
Tags: #Java #OpenJDK - Наука та технологія
I have hit this a few time and it can be annoying. This is a welcome change.
Oh a cyberpunk Fan and Fan of keep it simple concept. Like it ❤
Cool! About prologue you say: "static context plus a bit more". Can you please tell me what that "a bit more" is?
To answer the question at the start, me, very often even
Can we get a concrete newscast with several practical examples about how to use the new Classfile API, which is totally amazing. I really would like to try them out in my project, but there are so few information about how to use them, please!
I'm not the only one, who needs it 🙂
I do not know, if I use it for this() because it may be rearranged when it's complicated.
But for super() it's totally game changing.
No longer we will need (mostly) static constructor methods.
And no longer would we need auxiliary static methods
That No LTS always bring smile on my face man! good job though
Very handy and a welcome change.
In the past I might have created a factory method to handle parameter manipulation before invoking constructors to avoid this issue. This new functionality might obviate that need. However, the modern zeitgeist is a trend towards factory methods/builders and away from constructors, so this new functionality may be a little late. 🤷♂️
Interesting approach that improves readability.
Perhaps those cows are migratory and have flown South for the Winter? 🧐
static factories?
Gardaş eskiden super anahtar sözcüğünün üstünde kod yazılamıuor muydu?
Nice cows)
More feet will be shot because of this feature than toes saved by it.
How so?
I'M ON JAVA 8 :-)
Sen Türk müsün bıyıklı Java günleri İstanbul yazıyor t-shirt'ünde.
Buna kimse laf etmiş mi diye bakmıştım :)
moo();
I am not convinced this is a good change or will make anything easier. I worry this may lead to increased code complexity in overly aggressive inheritance models.
that was a looooooong talk, no code lol
No code? There is a lot of code in this video.
Typically Java…the medicine is worse than the disease
This is great! I once wanted to delegate to a constructor which takes in a JavaFX Button, but if I wanted to set add an image on that Button beforehand, I had to create an IIFE or a static method if I wanted to do that. e.g.
this(
((Supplier)() -> {
Button btn = new Button();
btn.setGraphic(graphic);
return btn;
}
).get(), func);
which is cursed
I am still not sure why this is relevant. It's good to hear a high level discussion which makes me think through what was said. It just seems like a complicated explanation about constructors that use more code than normal.
If your were to make a video about this, you'd want to target the general audiance regardless of their expertise on the subjet "constructor invocation", some people may not have heard about it before so you can't just drop the information without context. I don't find it complicated, half of the video is explaing how construtor currently work and why they are implemented the way they are. The other half is explaining the new feature and how it may or may not be useful.
A long time language user could also read the title and know exatly what this feature is about without watching the video, but like I said earlier, this is not given since the general audiance are not on the same expertise level.
The compromise is this "format"