Negative enumeration values on signed enums are returned as unsigned values when querying via the python api.

[cookiemon]

Version and Platform (required):

• Binary Ninja Version: 3.4.4193-dev
• OS: Fedora Linux
• OS Version: 37
• CPU Architecture: x64

Bug Description:
When defining signed enums with negative values, they show up as that inside the types window. But when querying the values via the python api, one gets the 64-bit two's complement representation.

Steps To Reproduce:
Run the following script in the python console with any binary opened:

builder = types.EnumerationBuilder.create(sign=True, width=2, members=[("first", -32)])
bv.define_user_type("foo", builder)
bv.get_type_by_name("foo").members[0].value

Expected Behavior:
The value returned by querying bv.get_type_by_name("foo").members[0].value returns -32, or at least is consistent with what's shown in the ui.

Screenshots:

Additional Information:
This behavior happens the same when you define enumerations via the ui and then query via the api.

[plafosse]

This was fixed somewhat recently latest dev (3.5) produces

>>> bv.types['foo']
<type: immutable:EnumerationTypeClass 'enum foo'>
>>> bv.types['foo'].members
[<BAR = -0x1>]
>>> bv.types['foo'].members[0]
<BAR = -0x1>
>>> bv.types['foo'].members[0].value
-1