The Elegance of Pattern Matching in Modern Java

preview_player
Показать описание

This presentation will examine the evolution of switch from a statement to an expression and on to powerful pattern-matching machinery in modern Java. You'll also explore the reasons to refactor code to use this elegant and concise feature.

Presented by Venkat Subramaniam - Founder, Agile Develper, Inc.

⎯⎯⎯⎯⎯⎯ More information ⎯⎯⎯⎯⎯⎯

Tags: #Java #OracleDevLive #Java18 #JDK18 #OpenJDK
Рекомендации по теме
Комментарии
Автор

So exciting to see the Java evolution! And as Venkat mentions in the end, imagine having things like destructuring in Java, dear lord, just can't wait to see it.

dcascato
Автор

I was waiting for several minutes for you to spot the superfluous "r" in "interger", and was very happy when you finally removed it.
Just for you to undo 20 seconds later and put it back in again :D

spheenik
Автор

Awesome presentation. What a pleasure watching venkat talks.

pmorah
Автор

Thank you, Venkat, it's an amazing presentation, enjoyed and learned new pattern matching in Java

kpradeep
Автор

Venkat is a great presenter. He's got a real infectious enthusiasm.

zaccicala
Автор

Can't wait to learn Java18 with Venkat!

shizhenglee
Автор

can you ask Venkat to use some IDE which uses syntax highlighting.. this will make code reading a lot better.. Presentation is really good.

badpotato
Автор

It is very interesting and push to have more elegance in coding. Perhaps it missing something on generic types.

luigibuoncristiani
Автор

How pattern matching is going to handle dynamic code and scenarios that can occurs with OSGi?

danieldudziak
Автор

Nice presentation. However, you should be aware most of the examples presented here violate Liskov substition principle. I hope I'll never see switch cases differentiating between interface implementations.

PandaMoniumHUN
Автор

Why is this called pattern matching ? I thought pattern matching was related to regex

roronoa_d_law
Автор

I do not understand why Venkat encourages us not to use default when an unexpected value is received. I always throw an IllegalArgumentException. That behaviour is future proof.

MrMikomi
Автор

Dr Subramaniam might not do Scala any more, but I guess he will admit that Scala's pattern matching is the best and although Java's pattern matching is nice, it's like a joke compared to the Scala one.

avalagum
join shbcf.ru