We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The formatting of the verilog files leaves a bit to be desired... At a minimum, there are pretty bad tab/space issues.
We already autoformat the C code, why not the verilog code?
At first pass, there is not a standard formatter people seem to use, so we'll have to find a suitable one.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The formatting of the verilog files leaves a bit to be desired... At a minimum, there are pretty bad tab/space issues.
We already autoformat the C code, why not the verilog code?
At first pass, there is not a standard formatter people seem to use, so we'll have to find a suitable one.
The text was updated successfully, but these errors were encountered: