Describe the change
Using string to represent value is a bad idea and it will cause challenges in the future. Porting to a separate class (Value) representation for the values will be useful. This will also fix the disallowed any expressions issue in mypy (added in PR for #35).
This requires changes to which of following?
This actually adds a new component:
[x] Value
A single PR should be submitted for all the parts. The commits need to be separate for all of them.
Note: You can only submit a patch if it is approved by one of the maintainers, otherwise the PR will be rejected.
Note: In the C, C++ and Python decompilers a namedtuple (ConstVal) is used to represent values, migrate this to Value too.
Describe the change Using string to represent value is a bad idea and it will cause challenges in the future. Porting to a separate class (
Value
) representation for the values will be useful. This will also fix the disallowed any expressions issue in mypy (added in PR for #35).This requires changes to which of following?
This actually adds a new component:
A single PR should be submitted for all the parts. The commits need to be separate for all of them.
Note: You can only submit a patch if it is approved by one of the maintainers, otherwise the PR will be rejected.
Note: In the C, C++ and Python decompilers a
namedtuple
(ConstVal
) is used to represent values, migrate this toValue
too.