You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it on purpose (to keep it private so you change it at the near future (or something like that))?
Can I open a PR adding the examples of the documentation? (or at least citing its existence)
I've found wrappable_struct! by navigating through the documentation and it was exactly what I was needing for my lib. It was really confusing how it worked (and I'm still not so sure of everything).
It seems to me like it "attaches" an amount of allocated raw memory to the Ruby object instance. And it puts a Rust struct on it. And the rutie/rust wrapper is able to "decode/dereference" this memory. It doesn't show in any instance variable or something (from the Ruby side).
Could you give me hints for a better understanding of the macro?
Can we document that on the Readme so it may be clear when to use it or not to use it?
The text was updated successfully, but these errors were encountered:
I think I can put some basic documentation about at the README. In a way that harmonizes with the remaining docs. I'll open a PR and we can discuss further.
Is it on purpose (to keep it private so you change it at the near future (or something like that))?
Can I open a PR adding the examples of the documentation? (or at least citing its existence)
I've found
wrappable_struct!
by navigating through the documentation and it was exactly what I was needing for my lib. It was really confusing how it worked (and I'm still not so sure of everything).It seems to me like it "attaches" an amount of allocated raw memory to the Ruby object instance. And it puts a Rust struct on it. And the rutie/rust wrapper is able to "decode/dereference" this memory. It doesn't show in any instance variable or something (from the Ruby side).
Could you give me hints for a better understanding of the macro?
Can we document that on the Readme so it may be clear when to use it or not to use it?
The text was updated successfully, but these errors were encountered: