# GC.@preserve macro equivalent for v0.6.2

**URL:** https://discourse.julialang.org/t/gc-preserve-macro-equivalent-for-v0-6-2/9647
**Category:** Internals & Design
**Created:** [March 11, 2018, 7:16pm UTC](https://discourse.julialang.org/t/gc-preserve-macro-equivalent-for-v0-6-2/9647 "2018-03-11T19:16:18Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![ScottPJones](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/scottpjones/32/146_2.png) [@ScottPJones](https://discourse.julialang.org/u/ScottPJones)
#### Post date: [March 11, 2018, 7:16pm UTC](https://discourse.julialang.org/t/gc-preserve-macro-equivalent-for-v0-6-2/9647/1 "2018-03-11T19:16:18Z")

</div>

I’ve been looking all over, and I can’t find any equivalent to the `GC.@preserve` macro that is in master.  
Do I just need to make some form of “no-op” macro to make things work on v0.6.2 (I don’t want to give up supporting that until v0.7/v1.0 is released, even though it is a bit of a hassle), or is there some equivalent?

---

<div class="post-metadata">

### Author: ![tkoolen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkoolen/32/1603_2.png) [@tkoolen](https://discourse.julialang.org/u/tkoolen)
#### Post date: [March 11, 2018, 7:45pm UTC](https://discourse.julialang.org/t/gc-preserve-macro-equivalent-for-v0-6-2/9647/2 "2018-03-11T19:45:37Z")

</div>

See [https://github.com/JuliaLang/Compat.jl/pull/491](https://github.com/JuliaLang/Compat.jl/pull/491), which proposes the no-op solution but is controversial.

---

<div class="post-metadata">

### Author: ![ScottPJones](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/scottpjones/32/146_2.png) [@ScottPJones](https://discourse.julialang.org/u/ScottPJones)
#### Post date: [March 11, 2018, 8:02pm UTC](https://discourse.julialang.org/t/gc-preserve-macro-equivalent-for-v0-6-2/9647/3 "2018-03-11T20:02:33Z")

</div>

Thanks! I hadn’t seen that discussion. Since I’m really just trying to keep it alive for testing on v0.6, not to make it really be robust on v0.6, but I do want it robust with the more aggressive GC on master, I think I’ll just go with a no-op on v0.6.
