Skip to content
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

Private vals don't get named by reflection nor @chiselName #1410

Closed
jackkoenig opened this issue Apr 10, 2020 · 3 comments
Closed

Private vals don't get named by reflection nor @chiselName #1410

jackkoenig opened this issue Apr 10, 2020 · 3 comments
Labels
Milestone

Comments

@jackkoenig
Copy link
Contributor

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

@mwachs5
Copy link
Contributor

mwachs5 commented Apr 10, 2020

There was a workaround for some other issue that was maybe relying on this behavior: #1352

@azidar azidar added this to the 3.4.0 milestone May 19, 2020
@seldridge seldridge added the bug label May 19, 2020
@seldridge
Copy link
Member

(Having not tested it and just looking through issues/PRs...) How does the Chisel naming plugin handle this? Does that close this issue?

@jackkoenig
Copy link
Contributor Author

Just checked, the plugin does indeed handle this!

Fixed by #1448

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants