The fallback version of nullptr provided by libc++ has a different mangled name than the real thing. This can cause ABI issues between code compiled in C++03 and C++11. This problem can be fixed when using Clang as the compiler. Clang provides 'nullptr' as an alternate keyword that is available in all C++ dialects. We should prefer using 'nullptr' instead of our own fallback type.
However this change is ABI breaking for any user who already depends the C++03 nullptr_t mangled name. Should we hold this change back until we better understand how to manage ABI changes?