Why does encode(to:) in an Encodable type take in an existential type?

[vanvoorden (Rick van Voorden)]

@itaiferber

As for whether this is possible today or not: it's possible to add generic overloads of init(from:) and encode(to:), but the calculus of performance benefit hasn't really changed. The cost of static vs. dynamic dispatch is pretty negligible, and in many cases, you end up with dynamic dispatch anyway.

AFAIK migrating away from existentials in some next-gen Codable would also help unblock bringing that to embedded.

JSON parsing on Embedded

Currently, without Foundation and Codable support, it's pretty hard to parse JSON in Embedded Swift. I've ported my JSON Tokenizer and parser, IkigaJSON, to work on Embedded Swift. The PR is still a bit early to tag, as I don't think it's convenient enough yet. My current train of thought is to add a macro that helps with (de)serialization of JSON in embedded mode. What are your thoughts?