Andrew Trick b73352af7a Disable Unsafe[Raw]BufferPointer testing in optimized mode. ...

The optimized-build behavior of UnsafeBufferPointer bounds/overflow
checking cannot be tested. The standard library always compiles with debug
checking enabled, so the behavior of the optimized test depends on whether
the inlining heuristics decide to inline these methods. To fix this, we need
a way to force @_inlineable UnsafeBufferPointer methods to be emitted inside
the client code, and thereby subject the stdlib implementation to the test
case's compile options.

2017-10-19 21:12:09 -07:00

26 KiB

Raw Blame History

View Raw