Skip to content

Conversation

@glopesdev
Copy link
Member

This PR adds an extra technical note about dynamic data object type signatures and a warning about their caveats and limitations regarding serialization and custom scripting extensions.

@glopesdev glopesdev added the documentation Improvements or additions to documentation label Jan 9, 2025
@banchan86
Copy link
Contributor

Hmm I have some trouble understanding what is going on in the first note, would it help to add an example bonsai workflow?

@bruno-f-cruz
Copy link
Collaborator

Hmm I have some trouble understanding what is going on in the first note, would it help to add an example bonsai workflow?

New (1 as Foo, "a" as Bar) != new("a" as Bar, 1 as Foo). These would be two distinct dynamic classes.

However if the order is the same, they evaluate to the same ephemeral type.

@banchan86
Copy link
Contributor

Hmm I have some trouble understanding what is going on in the first note, would it help to add an example bonsai workflow?

New (1 as Foo, "a" as Bar) != new("a" as Bar, 1 as Foo). These would be two distinct dynamic classes.

However if the order is the same, they evaluate to the same ephemeral type.

ah ok i got it now!

@glopesdev glopesdev merged commit 33c54a2 into main Jan 30, 2025
1 check passed
@glopesdev glopesdev deleted the data-object-notes branch January 30, 2025 09:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants