Use `CHECK{LITERAL}` in tests
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 524
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
There are bunch of tests like this:
```
// CHECK-NEXT: sv.verbatim "assign {{[{][{]0[}][}]}}.baz = {{[{][{]1[}][}]}}.{{[{][{]2[}][}]}}.{{[{][{]3[}][}]}};"
```
This is very hard to read. It is possible to simplify like this using LITERAL directive.
https://llvm.org/docs/CommandGuide/FileCheck.html#directive-modifiers
```
// CHECK-NEXT{LITERAL}: sv.verbatim "assign {{0}}.foo = {{1}}.{{2}}.{{3}};"
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the CIRCT test suite for CHECK directives with escaped literal braces like the example, then read the surrounding FileCheck tests and the LITERAL directive documentation. Replace applicable patterns with CHECK-NEXT{LITERAL} while preserving the expected output, and run the affected test commands to confirm they still pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100