Johannes Lund

Future of Decodable

5

- Would it be possible to gracefully migrate our syntax to rely on Swift 4's `Codable` instead? - Would there even be a point in doing that? (yes?)

This is an experiment to see what happens when we remove all existing functionality and rely on Swift 4's `Codable` instead. - [x] Remove all existing functionality - [x] Create...

- Replaces the role of `Any` with dedicated `JSON` struct, which itself is `Decodable` - Removes "closure-based error-path back-propagation" with the `JSON` struct appending paths on access. Worried how this...

We would perhaps soon have the opportunity to introduce subscripts as an alternative to operators. Here are some hasty thoughts: Pros: - Can record A LOT of metadata using implicit...

Remove default `Decodable` extensions

2

Re: #137 ## Extensions that can be removed - `Date` - `URL` - `String` - `Int` - `Double` - `Bool` ## Extensions that cannot be removed - `NSDictionary` - `NSArray`...

```swift func init(json: Any) throws { // Chooses Any-overload instead of generic overload => error try id = json => "object" => "id" } ``` Filed [SR-3148](https://bugs.swift.org/browse/SR-3148).

[WIP] Error formatter

1

The implementation is hideous, but it appears to work. ``` yaml object: | repo: | | owner:

Improve error messages

1

- lazy - fast - lots of stuff - display the important stuff - automatic We could retrieve type information in each => overload / equivalent Large dictionaries/arrays could be...

Before, the use of Foundation types `NSArray`, `NSDictionary`, `AnyObject` instead of Swift equivalents intentional, and important for performance. Now that [SE-0116](https://github.com/apple/swift-evolution/blob/master/proposals/0116-id-as-any.md) (if that's the right one) is implemented this should...

Strategy for dependency injection (if that's the correct term)

2

``` swift class A { var b: B } class B { weak var a: A let urlResponse: String } ``` Injecting parameters/dependencies in sub-objects of the objects being decoded...