Now incorrect type argument that looks like T<A><B> doesn't cause an assert, but just a parsing error.
Bug: 36224
Differential D42939
More correct handling of error cases C++ name parser eugene on Feb 5 2018, 4:49 PM. Authored by
Details Now incorrect type argument that looks like T<A><B> doesn't cause an assert, but just a parsing error. Bug: 36224
Diff Detail Event TimelineComment Actions Being more resilient when handling demangler outputs seems like a good thing, but I think it is important to understand what made the demangler produce that output in the first place, to make sure we aren't missing anything. Also, I think I found one more possible issue with this code.
|
While looking at the bug, this part here struck me as dubious.
Can you check that this properly handles a name like F<(3)>>(1)> f<3, 1>() (which is the demangled form of _Z1fILi3ELi1EE1FIXrsT_T0_EEv).