Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
test/SemaCUDA/constexpr-ctor.cu | ||
---|---|---|
14–27 ↗ | (On Diff #224225) | Do we really need three identical templates? If they are needed to let compiler emit multiple diagnostics, perhaps we could just add another template parameter so we can get different instantiations. |
test/SemaCUDA/constexpr-ctor.cu | ||
---|---|---|
14–27 ↗ | (On Diff #224225) | the error is emitted on the default ctor of the template. If we do not use different templates, all errors are emitted on the same line, we cannot make sure some instantiations do not cause error and some instantiations should cause error. Adding template parameter will not help, because the error will still be emitted to the same line. |
test/SemaCUDA/constexpr-ctor.cu | ||
---|---|---|
14–27 ↗ | (On Diff #224225) | Having multiple errors attributed to the same source is OK. You can specify expected count. E.g. You'll have different note diags emitted for individual errors, so checking them would both provide more info about that exactly the problem is and will verify that they are reported in the correct locations. Right now you are describing what/where triggers an error that as a comment. Letting compiler verify that instead would be better, IMO. |
test/SemaCUDA/constexpr-ctor.cu | ||
---|---|---|
14–27 ↗ | (On Diff #224225) | Yes I can use note. will do. |
LGTM.
Sometimes I wish it would be possible to specify some of the -verify diagnostics in temporal order, as opposed to tying them to locations. I.e. in this case it would be way more useful to see the call stack leading to the error at B::B. Oh, well.