Not a fan of the syntax, but also appreciate it's not just "string interpolation", it makes it very clear you're doing something different. I like that it's easily expandable and not too different from other languages that use r"Raw String here".
NOTE: String Template Processing is runtime, not compile time, as Mark was thinking, as with being able to work well with Freemarker templates – which may work, but not as I implied.
JEP 431: Sequenced Collections look like a nice improvement for consistency – annoying for library writers who may find it more useful, tho.
Mark: 440: Record Patterns and 441: Pattern Matching for switch – having used these a bit now I love them, in places they fit – they work well for Algebraic Data Type style things, but should be used in moderation tho.
Initially didn't think I'd find much interest in this, but the more I experiment with Dagger.IO pipelines, and with the forthcoming Java SDK I can see this being enjoyable.
Podden och tillhörande omslagsbild på den här sidan tillhör Mark Derricutt, Greg Amer and Richard Vowles. Innehållet i podden är skapat av Mark Derricutt, Greg Amer and Richard Vowles och inte av, eller tillsammans med, Poddtoppen.
