Namespacing Swift code with nested types
John Sundell

I like nesting types. I saw an issue however where the compiler was confused between a nested type and a non nested type with the same name. Imagine in your example you have a non-nested type called `Option` too. Does it conflict with the nested `Option`? If so, what are some different ways to resolve the conflict?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.