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
With #1050, you can have proc scoped type aliases.
But the DSLX formatter seems to shove the types and channels into one big blob and does not preserve user inserted line breaks.
proc Foo { type Bar = bits[32]; bar: chan<Bar> out; baz: chan<Bar> in; config(bar: chan<Bar> out, baz: chan<Bar> in) { (bar, baz) } init { () } next(state: ()) { } }
is reformatted to
Adding a comment like //Channels at least helps delineate where the channel declarations start.
//Channels
Preserve user line breaks which can be helpful for signifying different conceptual clusters of code.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What's hard to do? (limit 100 words)
With #1050, you can have proc scoped type aliases.
But the DSLX formatter seems to shove the types and channels into one big blob and does not preserve user inserted line breaks.
is reformatted to
Current best alternative workaround (limit 100 words)
Adding a comment like
//Channels
at least helps delineate where the channel declarations start.Your view of the "best case XLS enhancement" (limit 100 words)
Preserve user line breaks which can be helpful for signifying different conceptual clusters of code.
The text was updated successfully, but these errors were encountered: