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
Once #20234 merges, we'll have a split initialization model where native handles MemoryInit, and ChipStack handles the remaining bits needed for safe initialization of the stack. This is not ideal, since both are effectively serving two halves of the same initialization story.
We should remove native, and consolidate all initialization in ChipStack, and have each Python module effectively call into the ChipStack singleton to safely call into the SDK through ChipStack.Call or ChipStack.CallAsync methods.
The text was updated successfully, but these errors were encountered:
Problem
Once #20234 merges, we'll have a split initialization model where
native
handlesMemoryInit
, andChipStack
handles the remaining bits needed for safe initialization of the stack. This is not ideal, since both are effectively serving two halves of the same initialization story.We should remove
native
, and consolidate all initialization inChipStack
, and have each Python module effectively call into theChipStack
singleton to safely call into the SDK throughChipStack.Call
orChipStack.CallAsync
methods.The text was updated successfully, but these errors were encountered: