Fix message context

[vyasr]

Description

Resolves #514

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.
• The cmake-format.json is up to date with these changes.
• I have added new files under rapids-cmake/
  • I have added include guards (include_guard(GLOBAL))
  • I have added the associated docs/ rst file and update the api.rst

[KyleFromNVIDIA]

+1

I wonder if there would be a way to test this to make sure future macros don't have this problem...

[vyasr]

That's a good question. I'm not sure if there's an easy, semantically-aware solution. The simplest purely textual solution I could think of would be writing a pre-commit hook that just counts instances of the insertion and pop_back. There's probably an ideal middle ground that we could find.

[robertmaynard]

That's a good question. I'm not sure if there's an easy, semantically-aware solution. The simplest purely textual solution I could think of would be writing a pre-commit hook that just counts instances of the insertion and pop_back. There's probably an ideal middle ground that we could find.

I can't think of a nice way that doesn't include parsing the source code.

[vyasr]

/merge