Member functions and static variable definitions may use typedefs that
are private in the global context, but fine in the class context.
Details
Diff Detail
Event Timeline
| clang/lib/Parse/ParseTentative.cpp | ||
|---|---|---|
| 94 | I am wondering what is the false positive rate of this change? That is, if we enable incremental parsing by default (in a local build) and then run all tests which do not produce diagnostics. | |
| clang/test/Interpreter/disambiguate-decl-stmt.cpp | ||
| 74 | Could we move the diagnostic-producing cases in a separate file? | |
| clang/lib/Parse/ParseTentative.cpp | ||
|---|---|---|
| 94 | With this patch and enabling IncrementalExtensions by default, it's at least not worse than current main: For all of check-clang, I see a number of failing unit tests that start hoarding some memory and are killed with std::bad_alloc or are stuck using 100% CPU. Those we probably want to debug independently of this change... | |
| clang/test/Interpreter/disambiguate-decl-stmt.cpp | ||
| 74 | We could, but I'm actually not a big fan because it moves the expected failing test away from the related disambiguation tests above... | |
This change looks reasonable to me.
| clang/test/Interpreter/disambiguate-decl-stmt.cpp | ||
|---|---|---|
| 74 | Okay, fair enough. | |
I am wondering what is the false positive rate of this change? That is, if we enable incremental parsing by default (in a local build) and then run all tests which do not produce diagnostics.