What's Next - see PrivateDocuments file: _summary_vhdl_requirements_priority.xlsx
Further discussion of reflection into records.
Are variant records required?
Can we work with just typeish information (is_array, is_record sorts of things) or do we need to actually maintain the type at runtime?
'left and 'right are already carried for runtime introspection on array types, but this is an order of magnitude simpler than the variant data of an array
Can we come up with a simpler solution if the only goal is serialization/deserialization?
Requirements for this really need definition, or we're just going back and forth.
Doing this without copying would require the slice views to have to carry a lot of "stepping" information. Copying is simpler, but slow, and breaks the link to the source data.
Could slow down ALL array accesses. What would the performance implications be?
Can the problem be worked around with arrays of arrays?
This has had very little activity since 2004.
Arrays/composites of protected types.
Need some input from compiler writers as to why we currently disallow this.
Left off at 54.
Review and Approve Meeting Minutes:
Lieven approves, Ernst seconds.
Next Meeting: Thursday March 24, 2016 11 am Pacific