# Using \`'nonatomic\` foreign memory

**URL:** <https://racket.discourse.group/t/using-nonatomic-foreign-memory/787>\
**Category:** Questions & Answers\
**Tags:** question, ffi\
**Created:** [March 11, 2022, 5:14pm UTC](https://racket.discourse.group/t/using-nonatomic-foreign-memory/787 "2022-03-11T17:14:29Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![LiberalArtist](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/liberalartist/32/151_2.png) [@LiberalArtist](https://racket.discourse.group/u/LiberalArtist)\
**Post date:** [March 11, 2022, 5:14pm UTC](https://racket.discourse.group/t/using-nonatomic-foreign-memory/787/1 "2022-03-11T17:14:30Z")

</div>

Consider [this C type definition](https://github.com/libgit2/libgit2/blob/v1.4.2/include/git2/strarray.h#L22-L25):

```C
typedef struct git_strarray {
	char **strings;
	size_t count;
} git_strarray;

```

This called to mind the support added in [https://github.com/racket/racket/commit/87196e0144226b44fd4c00fcca26965458ae159d](https://github.com/racket/racket/commit/87196e0144226b44fd4c00fcca26965458ae159d) for ctypes like `(_list i _string)` as function arguments, but I realized I'm not quite sure about all the details of how to use it properly.

As I understand it, writing something like:

```racket
(define-cstruct _git_strarray
  ([strings (_list i _string)]
   [count _size])
  #:malloc-mode 'nonatomic)

```

would not work, because the `count` field is not a pointer, and [memory allocated in `'nonatomic` or `'interior` mode](https://docs.racket-lang.org/foreign/foreign_pointer-funcs.html#%28def._%28%28quote._~23~25foreign%29._malloc%29%29):

> is treated by the garbage collector as holding only pointers … The memory is allowed to contain a mixture of references to objects managed by the garbage collector and addresses that are outside the garbage collector’s space.

Is that true?

Does that mean I have to allocate the `_git_strarray` in `'atomic` (or `'atomic-interior`) mode and manually wrap things to manage the reference to the `strings` field (perhaps with `ffi/unsafe/alloc` and/or a hash table)?

Do I also have to allocate the memory for `strings` with `'interior`, since the collector wouldn't update the reference in the `git_strarray`?

And does that mean that I'd need to do basically the same thing for C structs like:

```C
typedef struct {
	unsigned int version;
	git_remote_callbacks callbacks;
	git_proxy_options proxy_opts;
	git_remote_redirect_t follow_redirects;
	git_strarray custom_headers;
} git_remote_connect_options;

```

that have a `git_strarray` in a field?

The foreign library never retains a reference to a `git_strarray` (or any structure containing one) across function calls, but some of these structures you'd want to create once and use many times. It would be nice to give the collector freedom to do its thing and minimize the amount of manual memory management.

I also have the sense that I'm overthinking this somehow …

---

_[View the full topic](https://racket.discourse.group/t/using-nonatomic-foreign-memory/787)._