Lines Matching refs:gpr_free

14 GRP-01-002 describes a programming pattern in gRPC Core where `gpr_free` is called and then the poi…
16 …ng it harder to generate memory-related bugs. There are also plans to remove `gpr_free` in general.
23 ### Alternative #1: Rewrite gpr_free to take void\*\*
24 One solution is to change the API of `gpr_free` so that it automatically nulls the given pointer af…
27 gpr_free (void** ptr) {
35 …gnificant concern as we are now unconditionally adding a store to every gpr_free call, and there a…
37 … called by the constructor initializer list. If this thing needs to be `gpr_free`'d using the prop…
39 Another concern is readability - this `gpr_free` interface is less intuitive than the current one.
43 ### Alternative #2: Add another gpr_free to the Core API
44 …n alternative `gpr_free` that nulls the given pointer is undesirable because we cannot enforce tha…
48 ### Alternative #3: Rewrite gpr_free to take void\*&
50 gpr_free (void*& ptr) {
55 …d furthermore is C89 non-compliant, which is a current requirement for `gpr_free`. Moreover, Googl…
59 …ve gRPC Core to C++ and smart pointers and the future work of removing `gpr_free` in general. We w…