Learn about all the cool new features of Scala 3 and how they impact your day to day development. This talk will refactor existing Scala code from 2 to 3, as well as outline transition process for projects.
We’ll cover the following:
Enums and Top level definitions
Deprecating implicits
Type system improvements (union, match, etc.)
Metaprogramming (inline, macros and typeclass derivation)
Additionally, we’ll give advice/guidance on adopting Scala 3 and evolving an existing project.
Josh Suereth is a Staff Software Engineer at Google LLC. He is a member of the Scala Language Improvement Process committee, and a contributor to open source. He’s the author of Scala in Depth, and currently tackling assistant technologies in his day to day work.
James Ward is a nerd / software developer who tries to share what he learns with others though presentations, blogs, demos, and code. After over two decades of professional programming, he is now a self-proclaimed Typed Pure Functional Programming zealot but often compromises on his ideals to just get stuff done. After spending too many sleepless nights in data centers repairing RAID arrays, he now prefers higher-level cloud abstractions with appropriate escape hatches. James is a huge Open Source proponent, hoping to never get burned by lock-in again.
Nguồn: https://ka-nom.com/
Xem thêm bài viết khác: https://ka-nom.com/game/
![[Phim Ngắn] Đừng Bắt Em Chờ | Phim Ngắn Tình Yêu – Cảm Động Rơi Nước Mắt – Hân – Nhà trọ Balanha](https://i.ytimg.com/vi/Hx6srEgYDMY/maxresdefault.jpg)
What about a way to tell the compiler "I want to write and define my value here" (inside a try statement, for example) "but actually have the scope be 1 level higher" , so I can use the afore-mentioned val outside the try statement?
Currently, I have to declare my instance to be a var, despite the fact it is only assigned once, and despite the fact that I could really use some help making sure that it IS properly assigned.
In similar thought, I would sometimes like to declare an instance inside a method, but have its value persist, as if I've declared it 1 level above. The C++ "static" keyword would fit the bill here, and at the same time relieve me of having to think up lots of unique names, or else be forced into create entire classes to get a similar "protected name" effect.
Int | String but still can pattern match over Boolean. Were the authors really preaparing for this presentation?
I was able to understand the talk and code unto 44:00