We map a "bits" type to a dedicated TypeObject. We already have a ScalarTypeObject specialization which has getValue() method. Examining the generated code for a , it creates this atrocity:
There are so many things wrong in this mapping it's not even funny. Let's evolve this thing into something sane in terms of interface modeling, implementation design as well as interactions with runtime.
We map a "bits" type to a dedicated TypeObject. We already have a ScalarTypeObject specialization which has getValue() method.
Examining the generated code for a , it creates this atrocity:
There are so many things wrong in this mapping it's not even funny. Let's evolve this thing into something sane in terms of interface modeling, implementation design as well as interactions with runtime.