Carrier Classes & Discussing Syntax
summary
Two recent Amber mails compare an original carrier classes draft that forces a full API contract (construction, representation, derived equals/hashCode) with a tighter followup that limits the class header to deconstruction only, leaving equals/hashCode and field mapping for later. Classes become deconstructible when a canonical constructor matching the component list exists, which unlocks reconstruction and marshaling for non‑records; the next preview targets imperative pattern matching via enhanced local variable declarations. This is a concrete design evolution, not a syntax-only debate.
AI-written summary · about
chapters (5)
- 0:00Intro
- 0:42Project Amber Recap
- 7:25Carrier Classes
- 27:22Syntax Discussions
- 42:06Amber Feature Preview
