Native Records
summary
Erlang gains a VM-level record type: native records are distinct from tuples and maps and require compiler and runtime support rather than being mere tuple sugar. The implementation in OTP 29 preserves pattern matching but changes allocation and layout, yielding measurable reductions in per-record memory and faster field access in benchmarks, at the cost of less runtime field dynamism; further allocation, GC and pattern-match optimizations are targeted for OTP 30 improvements.
AI-written summary · about
chapters (4)
related talks
42mBetter Modeling Through Records
44mUsing Record Types to Build Better Domain Models
14mTransitioning from Structural to Nominal Code with Efficient Gradual Typing
49mData-oriented Programming in Java
38mPattern Matching in Java: Better Code, Better APIs
41mOTP behaviours and how to behave around them
19mOTP Update
46mCreating Cloud Native Capabilities Using the Latest Features from Java and the JVM