Andrew Trick 9886e4ef54 Use UnsafeRawPointer in StringCore. ...

This is another necessary step in introducing changes
for SE-0107: UnsafeRawPointer.

UnsafeRawPointer is great for bytewise pointer operations.

OpaquePointer goes away.

The _RawByte type goes away.

StringBuffer always binds memory to the correct CodeUnit
when allocating memory.

Before accessing the string, a dynamic element width check
allows us to assume the bound memory type.

Generic entry points like atomicCompareExchange no longer handle
both kinds of pointers. Normally that's good because you
should not be using generics in that case, just upcast
to raw pointer. However, with pointers-to-pointers
you can't do that.

2016-07-27 09:07:35 -07:00

..

CMakeLists.txt

[SR-1738] add_swift_library takes SHARED/STATIC arg

2016-06-16 13:15:58 -04:00

GLKit.swift.gyb

Use UnsafeRawPointer in StringCore.

2016-07-27 09:07:35 -07:00