Lines Matching full:escapes

48 positives: when the list escapes, our ``RegionStoreManager`` is not magically
54 to cause pointer escapes (not only region changes) (which sounds like the right
56 triggering escapes when binding list elements to the list. However, it'd be as
57 conservative as the current patch's solution. Ideally, we do not want escapes to
59 escapes.
63 had neither pointer-type metadatas nor non-pointer escapes.
76 Approach (4): We could allow checkers to trigger pointer escapes in arbitrary
78 would be able to express facts like "when this region escapes, that metadata
186 pointer escapes then we shouldn't try to gin up storage for them just to get
260 symbols, escapes, invalidations, whatever.
291 > invalidated when a pointer escapes then we shouldn't try to gin up storage