Hi Vladimir,
> On Nov 9, 2017, at 8:36 AM, Vladimir Kushelkov via swift-corelibs-dev
> wrote:
>
> 1. Sometimes it is contently to be able to decode a struct or an object from
> a Foundation object (either NSArray or NSDictionary) that produce a valid
> JSON.
> For example, if I use a 3d party
Hi Luke,
Thanks for putting this together! In the meantime, CI testing has
highlighted an issue that will need to be solved before this can be
pulled in — namely that `NSKeyedUnarchiver` is currently incomplete as
it does not implement or override `failWithError` properly.
This is something w
Hi Luke,
Thanks for putting this together! Do you mind putting that up as a [pull
request](https://github.com/apple/swift-corelibs-foundation/pulls) so we
can review it more formally and run it through CI?
— Itai
On 22 Sep 2017, at 19:53, Luke Howard via swift-corelibs-dev wrote:
Had a cra
Hi Brandon,
Thanks for looking at this! We’ve got plans internally to potentially
add a strategy to `JSONEncoder`/`JSONDecoder` to allow lenient
conversions like this — i.e. implicitly stringify numbers (or parse
them from string input), among some others.
This would be opt-in for consumers of
>From my (potentially limited) experience, I would say that yes, many tools out
>there do follow this spec.
I only have anecdotal evidence to back this up, but I think many new tools use
this convention, and those that don't do not out of long-standing conventions
that say otherwise (e.g. `~/.vi
