You may not follow Swift Evolution. A lot of people don’t. It takes a lot of time and attention, and the signal-to-noise while good for lists of its type can be low for people with deadlines, managers, contracts, and real life.
So let me get to the point: do you have code that doesn’t or shouldn’t run in simulators? Maybe you’re building AVFoundation camera code or Metal or for the keychain or whatever? Instead of using tests like:
// Test for a simulator destination #if (arch(i386) || arch(x86_64)) && (!os(macOS)) // code suitable for simulator #else // code suitable for device #endif
wouldn’t it be a lot easier, more robust, and better for cross-platform development to have something simple like this?
// Test for a simulator destination #if targetEnvironment(simulator) // code suitable for simulator #else // code suitable for device #endif
If you think so, please send a note to firstname.lastname@example.org and mention your support of SE-0190. You can read the whole proposal at that link. Big thanks go to Graydon Hoare for his implementation.
Time is running short. Review ends on the 24th. This is very much a developer-driven proposal as opposed to a language-design proposal. I’d like to see Swift users have more presence in the SE community.
Call your Swift representative. ????