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
possible updates to how UGens are reference counted:
connections like => and =< are no longer ref-counted
when a UGen variable goes out of scope, it disconnects itself
this also means that shreds don't have to keep a special list of UGens created on it; however, need to handle cases when Shreds are removed explicitly (e.g., from otf/vm remove commands; stacks need unwinding, etc.)
need to verify with multichan UGens, chugens, chugraphs
it's still possible for make more than one connection between UGens, need to verify that disconnect removes all connections from POV of both endpoints
this might be an opportunity to streamline Chuck_UGen function names, semantics, and documentation
The text was updated successfully, but these errors were encountered:
possible updates to how UGens are reference counted:
=>
and=<
are no longer ref-countedThe text was updated successfully, but these errors were encountered: