# Advice for dealing with \`struct\` during development

**URL:** <https://discourse.julialang.org/t/advice-for-dealing-with-struct-during-development/21732>\
**Category:** New to Julia\
**Created:** [March 11, 2019, 11:16am UTC](https://discourse.julialang.org/t/advice-for-dealing-with-struct-during-development/21732 "2019-03-11T11:16:38Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![jacobadenbaum](https://avatars.discourse-cdn.com/v4/letter/j/5daacb/32.png) [@jacobadenbaum](https://discourse.julialang.org/u/jacobadenbaum)\
**Post date:** [April 10, 2021, 11:58pm UTC](https://discourse.julialang.org/t/advice-for-dealing-with-struct-during-development/21732/21 "2021-04-10T23:58:44Z")

</div>

So you mention in the README that one should be careful to remove the `@proto` macro after developing. Is this because there’s a known performance drop when using these kinds of proto-structs? Or is it just out of a sense of good programming hygiene?

P.S.  
This design seems really cool and a very clever way to get around the problem of needing to redefine structs.

---

<div class="post-metadata">

**Author:** ![BeastyBlacksmith](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/beastyblacksmith/32/4741_2.png) [@BeastyBlacksmith](https://discourse.julialang.org/u/BeastyBlacksmith)\
**Post date:** [April 11, 2021, 8:58am UTC](https://discourse.julialang.org/t/advice-for-dealing-with-struct-during-development/21732/22 "2021-04-11T08:58:47Z")

</div>

I haven’t made any tests about performance, but you add an extra layer of indirection and there will almost certainly be cases where this affects performance. Furthermore, once you are done prototyping it is an unneccessary complication.

[Previous page](https://discourse.julialang.org/t/advice-for-dealing-with-struct-during-development/21732.md?page=1)
