'Decodable' naming conflict in Swift 4

[chrismanderson]

Swift 4 includes a built in Decodable protocol. Tried to build my project in Swift 4/Xcode 9 and got naming conflicts all over the place.

Obviously, it's early, but wanted to bring this to everyone's attention! I'm not sure what development of this library will look like in the future but figured this issue could begin that conversation.

Thanks!

[GeorgeSealy]

I've seen the same - the compiler is unable to distinguish Decodable as either Swift.Decodable or Decodable.Decodable.

Specifying Decodable.Decodable doesn't help in this case - this may be a compiler issue as I feel this should work (happy to be corrected on this!)

[voidref]

Looks like this lib is going to have to do the Enum namespace hack, and come up with something besides Decodable for the namespace.

[nap-sam-dean]

You can work around this issue (for now) by importing just the protocol before importing the whole module:

import protocol Decodable.Decodable
import Decodable

This allows this struct to compile:

struct MyStruct: Decodable { ... }

Obvious caveats here, this might just be an implementation detail of Swift 4 and might stop working on the next Xcode 9 beta release.

[chrismanderson]

Doing import protocol Decodable.Decodable worked for me. Assuming it is not a permanent fix, but great to be be able to build my app in Xcode 9.

[Lascorbe]

What about DecodingError? Any (fast) workaround for that? :)

[nap-sam-dean]

import protocol Decodable.Decodable
import enum Decodable.DecodingError
import Decodable

[Lascorbe]

Weird, tried that and got an error, it works fine now tho. Thanks @nap-sam-dean! 🍻

[polqf]

FYI I opened a ticket in JIRA when I first got this error 😄
https://bugs.swift.org/browse/SR-5110

[Ankish]

It build and runs with this solution. If I try to Profile my app - profiling stops at
import protocol Decodable.Decodable - No Such module Decodable. Anyone checked this ?