> On Jan 5, 2018, at 23:43, David Hart wrote:
>
> I was really surprised when I saw that the release of 4.0 introduced this 3.2
> version to mean “the 4.0 compiler running in 3.1 compatibility mode”. So of
> course, I’m even more surprised to see a new 3.3 version. I find it very
> counter-i
Thanks for the info, Alan!
On `swift(<4.0)`: I think originally we were even more restrictive about how
people used `#if swift`, not even allowing !, &&, and ||. Without those
restrictions, allowing a `swift( and <= are
very deliberately not included, because people always forget point releases
I was really surprised when I saw that the release of 4.0 introduced this 3.2
version to mean “the 4.0 compiler running in 3.1 compatibility mode”. So of
course, I’m even more surprised to see a new 3.3 version. I find it very
counter-intuitive. It also means we will continue to have to incremen
Hey Jordan,
We tend to have to do major migrations of our Swift codebase, so I might be
able to help. For context at last count (February 2017 was the last time I
checked) we had 1.4m lines of Swift across our apps.
This means that when we migrate, we tend to have to chose the smallest possible
