An excellent issue report and set of pull-requests was recently submitted:
The issue report is in regards to the potential perils of including global custom C++11 literals, which we’re using to simplify syntax when specifying durations using std::chrono. Fortunately, there are now standardized duration literals in C++14 that are supported on all compilers we are currently targeting. By moving to C++14, we can use those standardized literals for time/duration, rather than creating our own.
So, we propose to target C++14 for the upcoming ROS 2 beta. There are a few other features that also seem quite nice in C++14 and could simplify/shorten the codebase over time, such as std::make_unique, return auto, and so on:
Because C++14 seems to be well-supported now by modern toolchains, we do not expect this to be disruptive to anyone . However, please discuss on this thread if you feel otherwise, so we can better understand your use case. Conversely, if you’re a big fan of C++14 for various reasons, please chime in!
 the potential breakages described in this post seem relatively minor: http://stackoverflow.com/a/23980931