Demangling of symbol causes recursive error

[nitnelave]

When trying to demangle the symbol
__ZN7ErrorOrIN5lexer5TokenENS0_8LexErrorEEC2IS2_EET_PNSt9enable_ifIXsr3std10is_base_ofIS2_NSt5decayIS5_E4typeEEE5valueEvE4typeE

I get error: demangling some part of the AST attempted to demangle itself again.

This is a symbol generated by clang++ (c++14), and I think corresponds to something like that:
template <typename E> ErrorOr<lexer::Token, lexer::LexError>::ErrorOr(E, typename enable_if<std::is_base_of<lexer::LexError, typename std::decay<E>::type>::value>::type) for some value of E (maybe lexer::LexError?)

[fitzgen]

Thanks for the bug report!

[fitzgen]

c++filt gives me:

ErrorOr<lexer::Token, lexer::LexError>::ErrorOr<lexer::LexError>(lexer::LexError, std::enable_if<std::is_base_of<lexer::LexError, std::decay<lexer::LexError>::type>::value, void>::type*)

[nitnelave]

I don't know what version of c++filt you are using, but the one I have (GNU c++filt 2.27) doesn't work (it doesn't recognize it as a symbol).

[nitnelave]

Tried it with a freshly-compiled GNU c++filt 2.28, same thing.

[nitnelave]

Tried it with c++filt from https://github.com/Chilledheart/llvm-tools with LLVM 3.7, didn't work.

[fitzgen]

OSX uses two underscores, other *nix use one underscore, so if you try removing one of the leading underscores, you'll probably have better luck. I was on OSX when I ran c++filt.

[khuey]

$ ./target/debug/examples/cppfilt __ZN7ErrorOrIN5lexer5TokenENS0_8LexErrorEEC2IS2_EET_PNSt9enable_ifIXsr3std10is_base_ofIS2_NSt5decayIS5_E4typeEEE5valueEvE4typeE
ErrorOr<lexer::Token, lexer::LexError>::ErrorOr<lexer::LexError>(std::enable_if<std::is_base_of<lexer::LexError, std::decay<lexer::LexError>::type>::value, void>::type*)