# What we need to do IO in Julia with guaranteed memory safety

**URL:** https://discourse.julialang.org/t/what-we-need-to-do-io-in-julia-with-guaranteed-memory-safety/9976
**Category:** Internals & Design
**Created:** [March 25, 2018, 11:57pm UTC](https://discourse.julialang.org/t/what-we-need-to-do-io-in-julia-with-guaranteed-memory-safety/9976 "2018-03-25T23:57:52Z")
**Posts on this page:** 1
**Showing post:** 5

<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 26, 2018, 4:37pm UTC](https://discourse.julialang.org/t/what-we-need-to-do-io-in-julia-with-guaranteed-memory-safety/9976/5 "2018-03-26T16:37:14Z")

</div>

I have a feeling from @jameson’s comments in the [other thread](https://discourse.julialang.org/t/reinterpret-to-a-single-value-from-an-array-of-a-smaller-data-type/9932/24) that I’m drastically underestimating the utility of `IO` objects. I think they may already do a lot of what I’m describing here. Will look into this more thoroughly and post back here.

The first potential worry that I’m seeing is that `read` essentially has `@noinline`, so that will limit things…

---

_[View the full topic](https://discourse.julialang.org/t/what-we-need-to-do-io-in-julia-with-guaranteed-memory-safety/9976)._