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
We need to have the associated assembly instructions modeled out for when users define an instance of data that exceeds 64 bits in size. It should probably interface with the memory allocator, though finding ways to store within 2-4 CPU registers might be acceptable (and even efficient).
The Types system needs to be more integrated within the expressions libraries (e.g. functions, constants). Type checking is not properly done yet for identifiers in many cases.
Note that this is NOT a duplicate of any other active issue, because it is specifically concerned with the assembly interactions for complex data structures. It is not concerned with implementing the TypeManager C/C++ backend, nor is it concerned with implementing type checking for an interaction.
The text was updated successfully, but these errors were encountered:
We need to have the associated assembly instructions modeled out for when users define an instance of data that exceeds 64 bits in size. It should probably interface with the memory allocator, though finding ways to store within 2-4 CPU registers might be acceptable (and even efficient).
The Types system needs to be more integrated within the expressions libraries (e.g. functions, constants). Type checking is not properly done yet for identifiers in many cases.
Note that this is NOT a duplicate of any other active issue, because it is specifically concerned with the assembly interactions for complex data structures. It is not concerned with implementing the TypeManager C/C++ backend, nor is it concerned with implementing type checking for an interaction.
The text was updated successfully, but these errors were encountered: