The issue is not clang 4 per se. It can be seen in the CRAN logs for quite a
few packages built with the clang 4 build from r.research.att.com, all of which
worked correctly with the LLVM distribution of clang 4.0.0 (and 4.0.1): the
latter required macOS Sierra (without saying so). And, as you
>From what I understand, the issue ultimately stems from the mixing of
different C++ standard library implementations: the system-provided
libc++, and the LLVM libc++ bundled with R.
A similar issue is described and investigated with the V8 package:
https://github.com/jeroen/V8/issues/37
Thi
