When creating a signal with shape set to an Enum-derived type, the decoder function is automatically inferred to a built-in function that turns the Enum value and name into a nice human-readable string.
When defining a layout with an field's shape set to an Enum-derived type though, the decoder inference doesn't happen. As far as I can see, this is because the Layout constructor will cast all fields' shapes with Shape.cast, resulting in the original Enum type being lost.
|
if not isinstance(shape, Layout): |
|
try: |
|
shape = Shape.cast(shape, src_loc_at=1 + src_loc_at) |
This results in an actual Shape object being passed to the Signal constructor, and thus the built in Enum decoder can't be used.
I can think of a few ways to fix this, but wanted to hear the maintainers' thoughts to see if they have a preferred way of going about it.
My first idea is to not cast shapes in the Layout constructor, but instead check whether the user-provided type is a valid shape, probably by calling Shape.cast, discarding the value, and checking for an exception.
The other idea is to add a field to Shape which stores the original type that a given object was casted from. This would also require some extra logic in the Signal constructor to not only check the shape's type when checking for default decoders, but also checking the original type of casted Shape objects.
Curious to hear any thoughts on this.
When creating a signal with
shapeset to an Enum-derived type, the decoder function is automatically inferred to a built-in function that turns the Enum value and name into a nice human-readable string.When defining a layout with an field's shape set to an Enum-derived type though, the decoder inference doesn't happen. As far as I can see, this is because the
Layoutconstructor will cast all fields' shapes withShape.cast, resulting in the original Enum type being lost.nmigen/nmigen/hdl/rec.py
Lines 48 to 50 in 8f5a253
This results in an actual Shape object being passed to the
Signalconstructor, and thus the built in Enum decoder can't be used.I can think of a few ways to fix this, but wanted to hear the maintainers' thoughts to see if they have a preferred way of going about it.
My first idea is to not cast shapes in the Layout constructor, but instead check whether the user-provided type is a valid shape, probably by calling Shape.cast, discarding the value, and checking for an exception.
The other idea is to add a field to Shape which stores the original type that a given object was casted from. This would also require some extra logic in the Signal constructor to not only check the shape's type when checking for default decoders, but also checking the original type of casted Shape objects.
Curious to hear any thoughts on this.