The thing I am worried about is that there may be other C++17 library features used by RLBox missing in MacOS 10.9... Did a quick pass on the features of libc++ version that ships with MacOs 10.9... - Looks like the last XCode to ship on this was 6.2 which used Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn). See [here](https://trac.macports.org/wiki/XcodeVersionInfo) for ref When I checked the libc++ feature version map [here](https://libcxx.llvm.org/cxx1z_status.html), one example of another thing that might break is "std::is_invocable" (earlier called "is_callable"). According to the link, this was shipped with libc++ 3.9 which was first included in XCode 8 as per [here](https://en.wikipedia.org/wiki/Xcode#Latest_versions), which in turn first showed up in OS X 10.11 per [here](https://trac.macports.org/wiki/XcodeVersionInfo). I think at this point, I want to confirm if the course of action is indeed - Fix all upstream uses of lib c++ 17 features newer than that of libc++ 3.5 (which shipped with MacOS 10.9) Or possibly - One of the other possibilities listed by Mike Hommey [:glandium] above
Bug 1573733 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The thing I am worried about is that there may be other C++17 library features used by RLBox missing in MacOS 10.9... Did a quick pass on the features of libc++ version that ships with MacOs 10.9... - Looks like the last XCode to ship on this was 6.2 which used Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn). See [here](https://trac.macports.org/wiki/XcodeVersionInfo) for ref When I checked the libc++ feature version map [here](https://libcxx.llvm.org/cxx1z_status.html), one example of another thing that might break is "std::is_invocable" (earlier called "is_callable"). According to the link, this was shipped with libc++ 3.9 which was first included in XCode 8 as per [here](https://en.wikipedia.org/wiki/Xcode#Latest_versions), which in turn first showed up in OS X 10.11 per [here](https://trac.macports.org/wiki/XcodeVersionInfo). I think at this point, I want to confirm if the course of action is indeed - Fix all upstream uses of lib c++ 17 features newer than that of libc++ 3.5 (which shipped with MacOS 10.9) Or possibly - One of the other possibilities listed by Mike Hommey [:glandium] above such as including a copy of libc++ in the distribution
The thing I am worried about is that there may be other C++17 library features used by RLBox missing in MacOS 10.9... Did a quick pass on the features of libc++ version that ships with MacOs 10.9... - Looks like the last XCode to ship on this was 6.2 which used Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn). See [here](https://trac.macports.org/wiki/XcodeVersionInfo) for ref When I checked the libc++ feature version map [here](https://libcxx.llvm.org/cxx1z_status.html), one example of another thing that might break is "std::is_invocable" (earlier called "is_callable"). According to the link, this was shipped with libc++ 3.9 which was first included in XCode 8 as per [here](https://en.wikipedia.org/wiki/Xcode#Latest_versions), which in turn first showed up in OS X 10.11 per [here](https://trac.macports.org/wiki/XcodeVersionInfo). I think at this point, I want to confirm if the course of action is indeed - Fix all upstream uses of lib c++ 17 features newer than that of libc++ 3.5 (which shipped with MacOS 10.9) Or possibly - One of the options listed by Mike Hommey [:glandium] above such as including a copy of libc++ in the distribution
The thing I am worried about is that there may be other C++17 library features used by RLBox missing in MacOS 10.9... Did a quick pass on the features of libc++ version that ships with MacOs 10.9... - Looks like the last XCode to ship on this was 6.2 which used Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn). See [here](https://trac.macports.org/wiki/XcodeVersionInfo) for ref When I checked the libc++ feature version map [here](https://libcxx.llvm.org/cxx1z_status.html), one example of another thing that might break is "std::is_invocable" (earlier called "is_callable"). According to the link, this was shipped with libc++ 3.9 which was first included in XCode 8 as per [here](https://en.wikipedia.org/wiki/Xcode#Latest_versions), which in turn first showed up in OS X 10.11 per [here](https://trac.macports.org/wiki/XcodeVersionInfo). I think at this point, I want to confirm if the course of action is indeed - Fix all upstream uses of lib c++ 17 features newer than that of libc++ 3.5 (which shipped with MacOS 10.9) Or possibly - One of the options listed by Mike Hommey [:glandium] above such as including a copy of libc++ in the distribution If the resolution here should be the former, will move this bug out of the "C++17 migration" task hierarchy into the "rlbox task hierarchy"