Catherine's latest activity
- 12mo ·
-
Public·
-
mastodon.social
@tenderlove @bascule@mas.to @thisismissem @bascule yes, that's correct. the exact same thing is necessary when wrapping JS, Lua, <...>, really any language with a GC'd heap. people do ship safe wrappers for these other languages (https://github.com/amethyst/rlua?tab=readme-ov-file#safety-and-panics is a good introduction), so it must be possible for Ruby as well
…See more
@tenderlove @bascule@mas.to @thisismissem @bascule yes, that's correct. the exact same thing is necessary when wrapping JS, Lua, <...>, really any language with a GC'd heap. people do ship safe wrappers for these other languages (https://github.com/amethyst/rlua?tab=readme-ov-file#safety-and-panics is a good introduction), so it must be possible for Ruby as well
See less
@tenderlove @bascule@mas.to @thisismissem @bascule yes, that's correct. the exact same thing is necessary when wrapping JS, Lua, <...>, really any language with a GC'd heap. people do ship safe wrappers for these other languages (https://github.com/amethyst/rlua?tab=readme-ov-file#safety-and-panics is a good introduction), so it must be possible for Ruby as well
@tenderlove @bascule@mas.to @thisismissem @bascule yes, that's correct. the exact same thing is necessary when wrapping JS, Lua, <...>, really any language with a GC'd heap. people do ship safe wrappers for these other languages (https://github.com/amethyst/rlua?tab=readme-ov-file#safety-and-panics is a good introduction), so it must be possible for Ruby as well
- 12mo ·
-
Public·
-
mastodon.social
@tenderlove @bascule @thisismissem I'm not sure I agree on the concept. Rust is, quite famously, well suitable for embedded devices full of unsafe code--I scrapped my own Ruby-like language that was too much like Rust in favor of pre-1.0 Rust--where you do need to consider the same concerns
interoperability with other languages is in the same area. just like with MCUs, someone needs to implement the interop once and others can (safely!) reuse it later
…See more
@tenderlove @bascule @thisismissem I'm not sure I agree on the concept. Rust is, quite famously, well suitable for embedded devices full of unsafe code--I scrapped my own Ruby-like language that was too much like Rust in favor of pre-1.0 Rust--where you do need to consider the same concerns
interoperability with other languages is in the same area. just like with MCUs, someone needs to implement the interop once and others can (safely!) reuse it later
See less
@tenderlove @bascule @thisismissem I'm not sure I agree on the concept. Rust is, quite famously, well suitable for embedded devices full of unsafe code--I scrapped my own Ruby-like language that was too much like Rust in favor of pre-1.0 Rust--where you do need to consider the same concerns
interoperability with other languages is in the same area. just like with MCUs, someone needs to implement the interop once and others can (safely!) reuse it later
@tenderlove @bascule @thisismissem I'm not sure I agree on the concept. Rust is, quite famously, well suitable for embedded devices full of unsafe code--I scrapped my own Ruby-like language that was too much like Rust in favor of pre-1.0 Rust--where you do need to consider the same concerns
interoperability with other languages is in the same area. just like with MCUs, someone needs to implement the interop once and others can (safely!) reuse it later