You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's confusing that there's slice for Logic and getRange for LogicValues. Also, that Logic has width and LogicValues has length. These, and maybe some other areas, should be made more consistent to reduce confusion. In some cases, maybe both should have both options (e.g. slice and getRange might be more useful in different scenarios but to both), and in other cases one should probably be deprecated and eventually removed.
Desired solution
Consistency between LogicValues and Logic where possible.
Alternatives considered
Leave things inconsistent. Original motivation was that LogicValues acts like a List and Logic acts more like SystemVerilog, but that might not be the right approach.
Additional details
Open to other suggestions!
The text was updated successfully, but these errors were encountered:
Motivation
It's confusing that there's
slice
forLogic
andgetRange
forLogicValues
. Also, thatLogic
haswidth
andLogicValues
haslength
. These, and maybe some other areas, should be made more consistent to reduce confusion. In some cases, maybe both should have both options (e.g. slice and getRange might be more useful in different scenarios but to both), and in other cases one should probably be deprecated and eventually removed.Desired solution
Consistency between
LogicValues
andLogic
where possible.Alternatives considered
Leave things inconsistent. Original motivation was that
LogicValues
acts like aList
andLogic
acts more like SystemVerilog, but that might not be the right approach.Additional details
Open to other suggestions!
The text was updated successfully, but these errors were encountered: