The changes in this paper add a new recommended practice. I had originally marked Clang as supporting this paper because we're not obligated to follow a recommended practice. However, in retrospect, it seems more useful to document whether we implement the recommendation or not. This adds a test for those changes. However, the recommended practice is just tricky enough to test, I wanted a second set of eyes on my test coverage to see if there's agreement I'm testing the right things and have come to the right conclusion.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
I had two suggestions for more tests, but this is probably covering everything.
clang/test/C/C2x/n2322.c | ||
---|---|---|
44 | I might suggest: _Static_assert(555 == \ Which, is basically exactly what the first bullet point in J.1 is trying to figure out (it should be the opening character). I think this is a repeat of the string-literal test, but it is basically exactly what they were talking about with PP-token. Not a great addition to this file perhaps, but something with #warning might be a nice exercise of the pp-directive, to make sure it hits the diagnostics engine right? |
Comment Actions
Committed in f1c9ef311fa677992798d609b0445f1d7311a8f2 (forgot to link the review with the commit message, sorry), thank you for the reviews!
I might suggest:
_Static_assert(555 == \
LI\
NE\
)
Which, is basically exactly what the first bullet point in J.1 is trying to figure out (it should be the opening character).
I think this is a repeat of the string-literal test, but it is basically exactly what they were talking about with PP-token.
Not a great addition to this file perhaps, but something with #warning might be a nice exercise of the pp-directive, to make sure it hits the diagnostics engine right?