-
Notifications
You must be signed in to change notification settings - Fork 604
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
Can't have a Vec(new Bundle{}) ? #1953
Comments
This error is stemming from:
|
rewriting the code to make the direction clear works to have an empty bundle in a Vec: |
12 tasks
What is the meaning of a |
Example showing this in v3.4.4: https://scastie.scala-lang.org/Up44My1rRiOkIlyWjpoMLw |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type of issue: bug report
Impact: unknown
Development Phase: request
Other information
If the current behavior is a bug, please provide the steps to reproduce the problem:
See this Scastie:
https://scastie.scala-lang.org/2qc4i466TRS9gvWIAnLmRQ
Note this is using Chisel 3.4.3 with the naming plugin enabled (same behavior seen without plugin enabled: https://scastie.scala-lang.org/XlNASbYNT6WDa641zN9kNQ)
Same code here:
What is the current behavior?
If I try to build a Vec(x, Bundle{}) I get a
None.get
error.What is the expected behavior?
Either I get a good error message about something I am doing wrong (unclear whether Vec-of-empty-bundle is allowed, when a Reg-of-empty-bundle works fine), or it works fine and I get registers-of-empty-bundles.
Please tell us about your environment:
Chisel 3.4.3, with naming plugin enabled
What is the use case for changing the behavior?
It is nice to be able to build up Bundles of optional fields or sequential fields which might end up that the Bundle itself has nothing in it and have things just work without special casing
The text was updated successfully, but these errors were encountered: