ref-struct | Create ABI-compliant struct '' instances on top of Buffers | Reflection library

I had almost got it:

This is because of the official version of FFI does not support electron 5. I asked on Github and got answered: https://github.com/electron/electron-rebuild/issues/308

I used an old version of electron and succeed.

A key factor here is size; Span / ReadOnlySpan are deliberately very small, so the difference between a span and a reference-to-a-span is tiny. One key usage for in here is for larger readonly structs, to avoid a significant stack copy; note that there's a trade-off: the in is really a ref, so you're adding an extra layer of indirection to all access, unless the JIT sees what you're doing and works some voodoo. And of course: if the type doesn't declare itself as readonly then a stack copy is automatically added before the call to preserve the semantics.

It is not field of your class but rather return value of a property getter - which is fine as it is just function return value.

Note that "as a member of a class" usually includes properties and probably should be changed to "field of a class".

If you would try to declare it as a class field (either directly or indirectly via auto-implemented property) this will require part of the class (the data for ref struct) to be allocated on the stack and the rest allocated in manged heap.

The code in the question defines non-autoimplemented property. As result there is no need for compiler to automatically create hidden field of the property type in the class. So while property result type is ref struct it actually is not stored in the class and hence does not violate requirement for this ref struct type not be included into any class. Note that even making setter method would be fine by itself - storing value for that property would be tricky, but you can safely store content of the ref struct (public int value; as in the post) in set and recreate it in get.

Remember that strings in Go are like slices. They are composed of a pointer to the backing data and the length. This is why in your code, GoString is defined as:

Finally I found out a solution for this.

learn.js

While ref, ref-struct and ref-array are powerful, but fragile things, their combination can behave really obscure.

There are two nuances with your sample:

1. Calling makeAccessContainerEntry twice overwrites your global cache - CStrings cached (global.x0 and global.x1) during the makeAuthGrantedFfiStruct call will be overwritten by the second directmakeAccessContainerEntry call.

2. It seems that you should cache each ContainerInfoArray too.

This code should work fine:

Solution: removes static keyword from functions :)

Looking at the documentation for ref.get(), you could use that: