> On Jun 1, 2016, at 9:15 AM, Erica Sadun wrote:
>
> Or, to be honest:
>
> /// Offers user-facing public assert configuration test
> @_transparent
> public
> func isDebugAssertConfiguration() -> Bool {
> return _isDebugAssertConfiguration()
> }
>
> which covers, I
Or, to be honest:
/// Offers user-facing public assert configuration test
@_transparent
public
func isDebugAssertConfiguration() -> Bool {
return _isDebugAssertConfiguration()
}
which covers, I believe, about 98% of the demand for this feature
-- E
> On May 31, 2016, at 11:21 PM, Brent
> My pitch: I want to promote these three helper functions to the standard
> library and remove their underscore prefixes.
These functions currently have implementations like this:
@_transparent
@warn_unused_result
public // @testable
func
Am I understanding correctly that
-Onone → _isDebugAssertConfiguration is true
-O → _isReleaseAssertConfiguration is true
-Ounchecked → _isFastAssertConfiguration is true
?
If the goal is to expose the optimization level to user code, might I
suggest something like
enum
Back in March, I somewhat foolishly agreed to pick up the gauntlet for a series
of community-requested proposals centered on build configurations. Requested
items included:
A way to test for destination platforms like Apple, Linux, Windows, Unix-like,
UIKit-supporting, etc
A way to test for