[c++] Rewrite bits of the verilator-support infrastructure to avoid exceptions
Open
Component:Tooling
Earlgrey-PROD Triaged
Good First Issue
Type:Cleanup
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
These aren't allowed by the Google style guide. Pointed out by @mcy in a recent review.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the verilator-support infrastructure and reviewing the referenced Google style restriction, then identify the scope of the rewrite and verify that the affected paths avoid exceptions without changing their existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100