Closed dzhu closed 6 years ago
+1
OS: Fedora 26 rtags: tag v2.18 Clang: 4.0.1
This seems to just work for me. I am running clang 6.0 however. Is it possible that your libclang doesn't support c++17?
Can you try to compile the example with the clang executable that goes with the libclang rtags is using?
Oops, rtags was compiled with libclang 3.8. Recompiling with 5.0 fixes it. Thanks!
Glad to hear.
Anders
On Tue, Mar 27, 2018 at 4:35 AM, dzhu notifications@github.com wrote:
Closed #1167 https://github.com/Andersbakken/rtags/issues/1167.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Andersbakken/rtags/issues/1167#event-1542995224, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEdSoHT3N8zdegzhTDa6R5omk1zX112ks5tiiP4gaJpZM4Sykdv .
Please mark appropriate
Problem description
When a file has
-std=c++17
in its compilation arguments, diagnostics appear in the file as if it is being treated as pre-C++11.Expected behavior/reproduction steps
a.cc
in emacs, containingusing x = int;
.echo 'g++ -std=c++17 a.cc' | rc -c
.Actual behavior
int
, with the minibuffer showingParse Issue: alias declarations are a C++11 extension: -Wc++11-extensions
.echo | rc
withc++11
orc++14
immediately causes the diagnostic to disappear, and rerunning withc++17
causes it to reappear.rtags-compilation-flags
andrtags-compile-file
know about the correct version in all cases.Environment