# openFile() and file.close() with different? Io objects

**URL:** <https://ziggit.dev/t/openfile-and-file-close-with-different-io-objects/13346>\
**Category:** Explain\
**Created:** [December 4, 2025, 2:40am UTC](https://ziggit.dev/t/openfile-and-file-close-with-different-io-objects/13346 "2025-12-04T02:40:56Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Sze](https://ziggit.dev/user_avatar/ziggit.dev/sze/32/496_2.png) [@Sze](https://ziggit.dev/u/Sze)\
**Post date:** [December 4, 2025, 1:04pm UTC](https://ziggit.dev/t/openfile-and-file-close-with-different-io-objects/13346/8 "2025-12-04T13:04:57Z")

</div>

I disagree, I think unmanaged is good (once you are used to it) and I think this existing topic is a good place to discuss it:

> [@Ergonomics of ArrayListUnmanaged](https://ziggit.dev/t/ergonomics-of-arraylistunmanaged/9777):
>
> This is a follow-up a post I read earlier: [Fastest way to 'switch' ownership of arraylist](https://ziggit.dev/t/fastest-way-to-switch-ownership-of-arraylist/9771). The topic of the post morphed into the use of multiple allocators with the various methods of ArrayListUnmanaged, and I wanted to follow up on this separately without contributing additional noise to the original topic. Specifically, I wanted to use something @ericlang said as a jumping-off point: Theoretically appending to the list isn’t a problem in-and-of itself. Since each allocator instance maintai…

---

_[View the full topic](https://ziggit.dev/t/openfile-and-file-close-with-different-io-objects/13346)._