The review of SE-0055 "Make unsafe pointer nullability explicit using Optional" ran from Mar 24…29, 2016. The proposal has been *accepted*:
The community and core team overall agree that it is best to make the null pointer processing more consistent (by eliminating types that can be nil, but which are not Optional). While UnsafePointer is disliked by many in the community, it is a necessary part of working with C APIs (as one prominant example). Making them work consistently with other types makes the language simpler and more predictable. This approach also dovetails well with the Clang nullability attributes, which allow auditing of C pointers.
Thank you to Jordan Rose for proposing this, and driving forward the implementation effort!