Add restriction on loop construct associated with DO CONCURRENT. Add couple of tests to ensure
clause validity checks.
The tests look good, just a few comments/queries?
I am really not familiar with canonicalization, but I could grasp what's defined in this patch.
If that's a restriction why is this not in the form of a semantic error message?
Which standard ?
A C++ beginners query -
nit:Was that or instead of and ?
The error message is issued in CheckDoConcurrentClauseRestriction in case there is a tile clause associated. Here we just bypass the logic and we do not issue the message a second time.
From no one all reference are from 3.1. Right now it's like a transition phase until patch D92120 is approved and landed.
std::holds_alternative would be fine in this case. I'll update the patch. Thx.
I just use the text from the standard. or would work as well.