A follow-up to Java Records deserve a mapper My earlier post introduced Immuto and made the general case for a mapper designed around Records from day one. This one is narrower and more specific: it walks through exactly where MapStruct , which is the mapper most Java teams already use, runs into friction with Records, with real annotations and real generated code on both sides. MapStruct is excellent. It’s been the go-to compile-time mapper for a decade, and it has supported Records ...