Mac OSX workaround possibly having issues with OSX 10.14.4

[ihowell]

So far, I've updated to OSX 10.14.4, updated xcode, launched xcode which installed further components, reinstalled the xcode command line tools, and installed the mac osx sdk headers package. I ran the workaround script to fill out .clang_complete, which resulted in the paths:

echo | clang -x c++ -v -E - 2>&1 | sed -n '/^#include </,/^End/s|^[^/]*\([^ ]*/include[^ ]*\).*$|-I\1|p'

-I/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1
-I/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/10.0.1/include
-I/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include
-I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include

(Note the update from clang 10.0.0 to clang 10.0.1)

Unfortunately, I am still getting odd errors coming from irony like this:

invalid operands to binary expression ('std::__1::ostream' (aka 'int') and 'const char [8]

std::cout << "Width: ";

I can confirm that these don't occur during compilation, as I've set and reset CC and CXX to LLVM's clang and I'm always able to fully compile the application without any of these errors. Am I missing something?

Edit: Not cc_args.py

[ihowell]

Closing. Apparently, Apple's clang++ 10.0.1 is just a lot pickier about imports than 10.0.0 was.