# Efficient reflection on structs

**URL:** <https://discourse.julialang.org/t/efficient-reflection-on-structs/55278>\
**Category:** Performance\
**Created:** [February 14, 2021, 9:24pm UTC](https://discourse.julialang.org/t/efficient-reflection-on-structs/55278 "2021-02-14T21:24:53Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![lmiq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lmiq/32/18314_2.png) [@lmiq](https://discourse.julialang.org/u/lmiq)\
**Post date:** [February 15, 2021, 7:43pm UTC](https://discourse.julialang.org/t/efficient-reflection-on-structs/55278/27 "2021-02-15T19:43:54Z")

</div>

A little bit offtopic, but you seem to be someone that will like to read these comments, as you seem to have interest in a deeper understanding and use of Julia:

> [@Julia's applicable context is getting narrower over time?](https://discourse.julialang.org/t/julias-applicable-context-is-getting-narrower-over-time/55042/57):
>
> That means you can do tricks that you just can’t do in a “higher” level language. Or you may be able to do but you have to tell the compiler “shut up I know what I’m doing.” This just isn’t true. Yes, Julia provides you with protections by default, but when the compiler can convince itself they aren’t necessary, they’re silently dropped. Here’s a case where I’ve not told the compiler @inbounds: julia\> function mysum(A) s = zero(eltype(A)) for a in A s += …

---

_[View the full topic](https://discourse.julialang.org/t/efficient-reflection-on-structs/55278)._