# Efficiently interpreting byte-packed buffer

**URL:** <https://discourse.julialang.org/t/efficiently-interpreting-byte-packed-buffer/78975>\
**Category:** Performance\
**Created:** [April 4, 2022, 2:18am UTC](https://discourse.julialang.org/t/efficiently-interpreting-byte-packed-buffer/78975 "2022-04-04T02:18:29Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://discourse.julialang.org/u/jules)\
**Post date:** [April 4, 2022, 2:47pm UTC](https://discourse.julialang.org/t/efficiently-interpreting-byte-packed-buffer/78975/16 "2022-04-04T14:47:36Z")

</div>

The answer is in this post [Constraints for `@generated` function - #3 by Chris\_Foster](https://discourse.julialang.org/t/constraints-for-generated-function/27967/3)

The generated function is not allowed to introduce a new type, and that’s what happens with a closure.

---

_[View the full topic](https://discourse.julialang.org/t/efficiently-interpreting-byte-packed-buffer/78975)._