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
Given an adequately clever parser and type constructor, we still cannot unambiguously recreate a data structure from the output of utter when there are pointers to non-pointer values.
In the case of pointers to concrete values, there is no address information given for the target, so for example:
To get this information and only report it where necessary we need to walk the structure once before the dump and mark concrete values that are referenced by a pointer.
Another complication is of how to deal with pointers into []byte. To not interfere with []byte formatting, I think the best approach is to add an appendix comment to []byte rendering to list elements that are referenced and their addresss.
The text was updated successfully, but these errors were encountered:
Given an adequately clever parser and type constructor, we still cannot unambiguously recreate a data structure from the output of utter when there are pointers to non-pointer values.
In the case of pointers to concrete values, there is no address information given for the target, so for example:
gives:
To get this information and only report it where necessary we need to walk the structure once before the dump and mark concrete values that are referenced by a pointer.
Another complication is of how to deal with pointers into []byte. To not interfere with []byte formatting, I think the best approach is to add an appendix comment to []byte rendering to list elements that are referenced and their addresss.
The text was updated successfully, but these errors were encountered: