News for hackers. Stuff that matters.
Re:Swift Generics Evolution by skohan on Monday April 15, 2019 @06:54AM (#19664441)
I believe that's incorrect. Swift generics deal with statically-knowable types.

My reading was:

`some` -> Some specific type with these constraints which will be known at compile time

`any` -> Any value conforming to these constraints which may vary at runtime

Re:Swift Generics Evolution by slavapestov on Monday April 15, 2019 @09:16AM (#19665043)
In the current “opaque types” prototype implementation `some` still hides the implementation of the type across module boundaries, meaning it can be changed without recompiling clients. The specific guarantee is that (in a single process execution) each invocation of a some-returning function returns the same concrete type.