Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
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
Expand list of files formatted by Verible #6031
Expand list of files formatted by Verible #6031
Changes from all commits
9a43e5f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could the formatter get rid of these extra unnecessary newlines?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that would actually be a useful feature! @hzeller
also, quick question: can the formatter replace tabs and trim trailing whitespace?
we see that creeping into the code base all the time...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC, if there are more than two newlines, they are compacted to two (but still leaving the freedom to the developer to distringuish between one line and 'more space'). @rkapuscik can probably confirm.
(But we are also currently avoiding re-formatting too long lines into multiple lines, so could be that this feature might not be active at this point as it involves line-break handling).
TAB -> space and removing trailing newline is handled by the formtter, yes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can the formatter align the brackets on these lines (51-58)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like the formatter is sometimes aligning brackets, but not in this case. Antmicro is looking into it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is controlled by
--named_port_alignment
option in Verible. By default it is set toinfer
(it was not explicitly set in the original formatter script), but if the consensus is to have named port connections aligned we can set it toalign
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for checking that @rkapuscik. I opened lowRISC/style-guides#48 to get indication on which style we prefer, but for this PR the change is fine as-is: it keeps the existing style for this particular instantiation (which is non-tabbed), and just applies this rule consistently.