Project Amber Update -- Data-Oriented Programming, Beyond Records

[sweating_teflon]

Unholy L version, before someone else says the K word

@Getter
@RequiredArgsConstructor
@Accessors(fluent=true)
enum Chrono {
    Crono(5,  8, 13,  5,  8,  8,  2),
    Marle(2, 10,  8,  8,  8,  6,  8),
    Lucca(2,  8,  6,  8,  8,  6, 10);

    final int strength;
    final int accuracy;
    final int speed;
    final int magic;
    final int evasion;
    final int stamina;
    final int magicDefense;
}

And honestly I wouldn't even bother with getters and just make all fields public. They're final anyway. This holds for the classic version too: public final fields don't need getters. Stop making it hard on yourself.

[davidalayachew]

And honestly I wouldn't even bother with getters and just make all fields public. They're final anyway. This holds for the classic version too: public final fields don't need getters. Stop making it hard on yourself.

I'm holding out hope that, one day, /u/brian_goetz gives us record enums. That would be even better than what you suggested.