Replies: 1 comment 1 reply
-
I agree, things like this can be pretty hard to debug if you're not aware of this behavior. Related issue: #142 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The
Const()
Logic in ROHD required explicit width declaration when width greater than one. I am not sure whether this is a bug? Shouldn't thatConst(4)
throw an error since this is invalid due to its actuallyConst(4, width: 1)
which shows value of 0 instead. It's hard to identify the bug when the design is big, and the user accidentally forgets to assign the width.I am thinking that we can create a feature that helps them resolve the width at the backend. Or throw an error/warning when user perform this kind of behavior. At least better than current silently make it become
0
. Or is there already existing function built that I am not aware?https://dartpad.dev/?id=70c8dc936001270a03dac68c92a44f06
Beta Was this translation helpful? Give feedback.
All reactions