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
This is the "later" follow up ticket to the "take out metadata to start with and make opaque later #31".
One use case of being able to "take the entire metadata" is keeping around data that is set for the lifetime of a resource, so a library may want to "1) store it 2) run user code, allowing it to shadow or remove metadata etc 3) restore the metadata for the next invocation"
This pattern is sometimes useful, and would be nice if we could support it, esp since without a "give me the metadata" a framework can not implement this without knowing all the keys that it should keep+restore.
This is the "later" follow up ticket to the "take out
metadata
to start with and make opaque later #31".One use case of being able to "take the entire metadata" is keeping around data that is set for the lifetime of a resource, so a library may want to "1) store it 2) run user code, allowing it to shadow or remove metadata etc 3) restore the metadata for the next invocation"
This pattern is sometimes useful, and would be nice if we could support it, esp since without a "give me the metadata" a framework can not implement this without knowing all the keys that it should keep+restore.
Example test:
The text was updated successfully, but these errors were encountered: