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
{{ message }}
Repository navigation
Support bounded arrays of shared-memory pointers in enum payloads #749
Enum payload lowering currently supports shared-memory pointer leaves directly and through ordinary struct/tuple nesting by using target-stable generic-pointer physical storage and reconstructing the semantic address space at enum construction and extraction boundaries.
Arrays containing shared-memory pointers are still rejected.
unsupported even though the existing recursive storage conversion can reconstruct aggregate values element by element.
Why this needs an explicit bound
Array reconstruction is performed in SSA. Each shared-pointer leaf requires aggregate extraction/insertion around an address-space cast, so accepting arbitrary arrays would allow type size to translate directly into unbounded generated code and verifier work.
The support should therefore remain fail-closed unless the recursive array shape stays within an explicit expansion bound.
The bound should count shared-pointer leaves recursively rather than only the outer array length. For example:
Activity