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 most egregious example is in Queue which uses private vals. Now perhaps we should just make them public, but the issue still stands.
Queue
Long ago, Chisel reflective naming worked on private val (#407), it seems this is no longer true.
private val
It's also of note that @chiselName doesn't name private vals.
@chiselName
I feel like both of these are bugs that should be fixed.
Type of issue: bug report
Impact: API addition (no impact on existing code)
Development Phase: request
The text was updated successfully, but these errors were encountered:
There was a workaround for some other issue that was maybe relying on this behavior: #1352
Sorry, something went wrong.
(Having not tested it and just looking through issues/PRs...) How does the Chisel naming plugin handle this? Does that close this issue?
Just checked, the plugin does indeed handle this!
Fixed by #1448
No branches or pull requests
The most egregious example is in
Queue
which uses private vals. Now perhaps we should just make them public, but the issue still stands.Long ago, Chisel reflective naming worked on
private val
(#407), it seems this is no longer true.It's also of note that
@chiselName
doesn't name private vals.I feel like both of these are bugs that should be fixed.
Type of issue: bug report
Impact: API addition (no impact on existing code)
Development Phase: request
The text was updated successfully, but these errors were encountered: