# Big overhead with the new lazy reshape/reinterpret

**URL:** <https://discourse.julialang.org/t/big-overhead-with-the-new-lazy-reshape-reinterpret/7635>\
**Category:** Internals & Design\
**Created:** [December 8, 2017, 8:02pm UTC](https://discourse.julialang.org/t/big-overhead-with-the-new-lazy-reshape-reinterpret/7635 "2017-12-08T20:02:20Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![ExpandingMan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/expandingman/32/866_2.png) [@ExpandingMan](https://discourse.julialang.org/u/ExpandingMan)\
**Post date:** [March 21, 2018, 2:38pm UTC](https://discourse.julialang.org/t/big-overhead-with-the-new-lazy-reshape-reinterpret/7635/14 "2018-03-21T14:38:55Z")

</div>

I was wondering if there has been any further progress or investigation on this?

I’m getting some segfaults I can’t figure out so more than ever I’m itching to be able to use reinterpret. I’ve had a very hard time figuring out what about `reinterpret` is even slow. Sometimes accessing individual elements seems perfectly fine, but then I’ll run it through a function or something and it’s inexplicably slow.

---

_[View the full topic](https://discourse.julialang.org/t/big-overhead-with-the-new-lazy-reshape-reinterpret/7635)._