2 Commits

Author	SHA1	Message	Date
Arnold Schwaighofer	da6d9152b6	Differentiate between user assertion and preconditions and the like ... assert() and fatalError() These functions are meant to be used in user code. They are enabled in debug mode and disabled in release or fast mode. _precondition() and _preconditionFailure() These functions are meant to be used in library code to check preconditions at the api boundry. They are enabled in debug mode (with a verbose message) and release mode (trap). In fast mode they are disabled. _debugPrecondition() and _debugPreconditionFailure() These functions are meant to be used in library code to check preconditions that are not neccesarily comprehensive for safety (UnsafePointer can be null or an invalid pointer but we can't check both). They are enabled only in debug mode. _sanityCheck() and _fatalError() These are meant to be used for internal consistency checks. They are only enabled when the library is build with -DSWIFT_STDLIB_INTERNAL_CHECKS=ON. I modified the code in the standard library to the best of my judgement. rdar://16477198 Swift SVN r18212	2014-05-16 20:49:54 +00:00
Dave Abrahams	3de27d2179	[stdlib] Array: add bridgeCache/fix refCounting ... Array's getObjects:range: needs to fill the supplied buffer without incrementing the reference count. For that reason, and to fulfill lifetime expectations for Array elements that are computed dynamically (e.g. from value types that are BridgedToObjectiveC), we maintain a cache of converted objects associated with each Array. Swift SVN r16105	2014-04-09 07:59:43 +00:00