Today I am reminded, once again, that #Codable is a terrible #SwiftLang API that should be excised from the language with extreme prejudice.
It's a shame that Swift 6 is already "doneβ; it would've been the perfect time to do it.
=> More informations about this toot | More toots from davedelong@mastodon.social
@davedelong Hey Dave! π Can you expand on this or link to something that would explain the issues? π This opinion has made me very curious and I'd love to know more!! π
=> More informations about this toot | More toots from MikeMcNamara@mastodon.social
@davedelong Why is it bad? I only want stuff serialized.
=> More informations about this toot | More toots from HanBrolo@techhub.social
@davedelong have you considered this? https://github.com/SwiftyLab/MetaCodable
=> More informations about this toot | More toots from maccatalan@techhub.social
@davedelong Iβd love to hear the thoughts behind this.
I have some issues with it, particularly that it has to be a conformance, and in creating custom coders (non json, say).
It also feels both not powerful enough and too powerful, has a few irritating edge cases (eg, around nullify), and is just, like, quite heavy feeling internally, and a bit odd.
I like that it mostly just works though. Thatβs okay.
=> More informations about this toot | More toots from benjohn@todon.nl
@davedelong I love my Codable.
=> More informations about this toot | More toots from Migueldeicaza@mastodon.social This content has been proxied by September (ba2dc).Proxy Information
text/gemini