Otherwise the source range of the passed-in ParsedAttributesWithRange
ends up being invalid and the resulting error messages rather useless.
For example:
error: fallthrough annotation in unreachable code [-Werror,-Wimplicit-fallthrough]
Instead of the more useful error message, which is produced with this
commit:
./test.c:8:5: error: fallthrough annotation in unreachable code [-Werror,-Wimplicit-fallthrough]
__attribute__((fallthrough)); ^
Can we add a comment above here saying that use of this interface is discouraged and callers should use the interface that takes the attributes with range information. Eventually, we should be getting rid of the range-less parsing functionality.