I really like this idea of scoped import, but I’m not sure it’s part of
anything supported widely. I was about to suggest ‘namespaces’ but that’s not a
thing in swift.
On Nov 9, 2017, 17:06 -0500, Rod Brown , wrote:
>
> > On 7 Nov 2017, at 6:24 am, Tony Parker via swift-evolution
> > wrote:
>
> On 7 Nov 2017, at 6:24 am, Tony Parker via swift-evolution
> wrote:
>
> Hi Florent,
>
> We definitely thought about this while designing the set of types with the
> Codable proposals.
>
> One serious concern was just how much API surface area there already is with
> Codable. If we open up
Hi Florent,
We definitely thought about this while designing the set of types with the
Codable proposals.
One serious concern was just how much API surface area there already is with
Codable. If we open up the internal classes as well, we risk confusing the
majority of people who are just adop
At Swift Summit, we discussed with Joe and Jordan about opening up the
Encoder/Decoder classes in order to make the work of an encoder designer easier.
As I was working on an API project, I found myself into the situation of
needing to tweak so slightly the encoding strategy this required a full
