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
Currently a parent Account has a owned clone of all the child's settings even when there are multiple levels of nested Accounts, making it so that the same setting exists multiple times needlessly.
Ideally we would make it so we have a reference in the parent Account of a setting present in the child Account
Solutions could be:
An Account having an OwnedSettings, and RefSettings, this would be solving the problem of what to do when .insert() is called in an Account holding child Accounts.
Alternatively just one HashMap exists, but swapping the V in HashMap<K,V> for an Rc<V> or Rc<RefCell<V>>
The text was updated successfully, but these errors were encountered:
OxidizedLoop
changed the title
Prevent duplication of settings when child Accounts exist
Stop Clonning values of settings in child Accounts
Jan 28, 2024
Currently a parent
Accounthas a owned clone of all the child's settings even when there are multiple levels of nestedAccounts, making it so that the same setting exists multiple times needlessly.Ideally we would make it so we have a reference in the parent
Accountof a setting present in the childAccountSolutions could be:
An Account having an OwnedSettings, and RefSettings, this would be solving the problem of what to do when .insert() is called in an
Accountholding child Accounts.Alternatively just one
HashMapexists, but swapping theVinHashMap<K,V>for anRc<V>orRc<RefCell<V>>The text was updated successfully, but these errors were encountered: