Version of the language is no longer supported by the Ruby developers it is not Magnus currently works with, and is still tested against, Ruby 2.7, but as this Ruby versions 3.0, 3.1, and 3.2 are fully supported. This, but users of Magnus should be able to do most things without needing to The unsafe keyword, it is impossible to interact with Ruby's C-api without Magnus itself contains a large amount of code marked with Other than this, Magnus strives to match Rust's usual safety guaranties for This would leave no way to differentiate the really unsafeįunctions that need much more care to use. While it would be possible to mark any functions that could expose this unsaftyĪs unsafe, that would mean that almost every interaction with Ruby wouldīe unsafe. It is not possible to enforce this rule in Rust's type system or via the borrowĬhecker, users of Magnus must maintain this rule manually.Īn example of something that breaks this rule would be storing a Ruby object inĪ Rust heap allocated data structure, such as Vec, HashMap, or Box. Objects are moved to the heap the Ruby GC can not reach them, and they may be When using Magnus, in Rust code, Ruby objects must be kept on the stack.

Download ruby types