Ignacio Encinas Rubio
Ignacio Encinas Rubio
Fixes https://github.com/chipsalliance/verible/issues/1278 Currently, case-missing-default rule requires the `default` case for every case statement. This PR makes an exception for `unique case` statements as requested by the issue. I also changed...
Up until now, constraint-name-style rule required constraint names to end in `_c`. This makes it configurable, so that users can require constraint names to start with `c_` instead. I'm open...
There are several "name style rules" and one more being developed (https://github.com/chipsalliance/verible/pull/1983) which have their rules hardcoded or with small configuration capabilities. In the past, this motivated a PR that...
This recently added rule inspired by a [clang-tidy](https://clang.llvm.org/extra/clang-tidy/checks/bugprone/suspicious-semicolon.html) seems a good candidate for being enabled by default. Only one "possible" false positive, and could potentially save hours of staring at...
**Summary** When adding test cases for SyntaxTreeRules, in my experience, it is not so difficult to have some syntax errors inside the test cases due to how they're written. When...
https://github.com/chipsalliance/verible/blob/master/doc/development.md already contains some tips useful for newcomers. Maybe it would be worth pointing to https://github.com/chipsalliance/verible/blob/master/.github/bin/make-compilation-db.sh to show how to create a compilation database for clang tooling.
Addresses https://github.com/chipsalliance/verible/issues/1913 with some minor changes - Suffixes are totally configurable, and different styles can be combined. - If a parameter (input/output) is set to "", no checks are performed....
This PR adds autofixes for every case currently flagged in always_ff_non_blocking_rule. ~I added a separate formatting commit just in case it made review easier.~ Quick summary: - Added getters for...