Lines Matching refs:pointer

381 This approach proves to be particularly useful for modeling pointer values,
403 Output parameters are function parameters of pointer or reference type whose
413 For example, in the following code snippet the pointer `c` is an output
469 Functions that escape the pointer also block the refactoring:
483 *   Find a function with a non-const pointer or reference parameter.
492 *   Prove that the function does not persist the pointer in a data structure
507 states accumulate observed violations (unsafe reads and pointer escapes) that
521 symbolic evaluation of `DeclRefExpr`s, `LValueToRValue` casts, pointer
683 to pointer states:
704 Let's look at an example where the raw pointer owns two different memory blocks:
733 In the following example, the raw pointer is used to access the heap object
752 introduce a non-owning pointer variable, since we can't use the moved-from
787 This analysis will refuse to refactor code that mixes borrowed pointer values
789 pointer, which is assigned to `pi`. Then, `pi` is used to hold a uniquely-owned
790 pointer. We don't distinguish between these two assignments, and we want each
792 pointer to a `Conflicting` state, like in this example.