As part of an API CasePath is awesome (I want it on the language!!) but I'm still not sure about using it in the wild, as opposed to code generated accessors.
Let's explore a real world application of "case paths," which provide key path-like functionality to enum cases. We'll upgrade our composable architecture to use them and see why they're a better fit than our existing approach.
I like that we can do this, but maybe a property on the enum itself would be nicer, and that without code generation (or lang support) seems really tricky to pull off.
That said, I really like this small addition makes if with enums so much nicer! <3
(is it worth adding @firstname.lastname@example.org ?)
@email@example.com If only we could extend all types, or all enums, etc... for such amazing extension capabilities that @SwiftLang@twitter.com has I sometimes miss this one.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!