I’m currently -1 on this, because I don’t think simulator/device is a worthwhile-enough distinction for a built-in condition.
- Are you maybe looking for a Debug/Release condition? Because we already have that, through compile-time variables (the “-D” option). - Does your platform’s simulator/emulator expose any additional API? Great! Take a look at #canImport… - Why else would you need to distinguish simulator/device, and why are OS and architecture not sufficient for that case? Karl > On 25. Oct 2017, at 05:05, Graydon Hoare via swift-evolution > <[email protected]> wrote: > > Hi, > > I'd like to propose a variant of a very minor, additive proposal Erica Sadun > posted last year, that cleans up a slightly messy idiomatic use of > conditional compilation in libraries. The effects should be quite limited; > I'd call it a "standard library" addition except that the repertoire of > compiler-control statements isn't strictly part of the stdlib. > > Proposal is here: > https://gist.github.com/graydon/809af2c726cb1a27af64435e47ef4e5d > <https://gist.github.com/graydon/809af2c726cb1a27af64435e47ef4e5d> > > Implementation (minus fixits) is here: > https://github.com/graydon/swift/commit/16493703ea297a1992ccd0fc4d2bcac7d078c982 > > <https://github.com/graydon/swift/commit/16493703ea297a1992ccd0fc4d2bcac7d078c982> > > Feedback appreciated, > > -Graydon > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
