http://llvm.org/bugs/show_bug.cgi?id=21656
Kaelyn Takata <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Kaelyn Takata <[email protected]> --- Indeed it was fallout in the form of a code path not covered by any of the regression tests where a type-dependent TypoExpr node would be seen by a non-C++ code path that tried to check the expression's type and failed. I've fixed this case and added a test in r222694. As an aside, the assertion in ~Sema from r222552 would have been triggered if asserts were enable, highlighting the fact that a typo had been encountered but never corrected (i.e. a TypoExpr was created but never diagnosed) and providing a better indication of what went wrong than the generated error message had. ;) -- You are receiving this mail because: You are on the CC list for the bug.
_______________________________________________ LLVMbugs mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
