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
It's currently possible for containers to be nested somewhat deeply as nested types are coded, potentially creating a non-trivial amount of cpu + memory overhead. Much of the container behavior has been added in order to support limiting container sizes, which has both practical and safety benefits. The goal of this issue is to find a way to reduce the number of nested containers and any associated overhead.
The text was updated successfully, but these errors were encountered:
It's currently possible for containers to be nested somewhat deeply as nested types are coded, potentially creating a non-trivial amount of cpu + memory overhead. Much of the container behavior has been added in order to support limiting container sizes, which has both practical and safety benefits. The goal of this issue is to find a way to reduce the number of nested containers and any associated overhead.
The text was updated successfully, but these errors were encountered: