Viewing profile — matsadler

I don't know why this caught HN's attention today, but I first found out about the Halton sequence a number of years ago when I needed a random seeming, regularly distributed and s…

The template generated with bundle gem —-ext=rust uses the Magnus[1] library that provides a high-level friendly Rust wrapper over the Ruby C API, but you can also use rb-sys[2] wh…

Add support for bundle gem --ext=rust command. Cool to see support for writing extension gems in Rust shipping with Ruby.

https://github.com/ankane/tokenizers-ruby

I think the goal of this right now is just to match the C version. The C implementation of YJIT supported x86 Unix/Linux platforms, and it sounds like adding Windows and arm64 supp…

Here's an example that shows x ||= y behaves like x || x = y, rather than x = x || y class Foo def foo=(object) puts "foo= called with #{object.inspect}" @foo = object end def foo …

For the cases I have benchmarked concatenation with Here's a simple benchmark: require "benchmark" n = 100_000 Benchmark.bm(4) do |x| x.report(" The results I get for this are: use…

I've not read the code, so someone may have to correct me, but I think this is the gist of it: Ruby 2.1 introduces a generational garbage collector, this divides all objects into y…

#reachable_objects_from was added in 2.0, and I think #memsize_of was introduced in one of the 1.9 releases. The documentation is new though. I wrote a little about them here: http…

You're correct, that is the default behaviour of super. My intention wasn't to say that super only works like that when you've defined the method like `def foo( * )` but rather `de…

(context: I'm the author) I do agree with you, but through some failing of my own I still quite enjoy that trick. I included it to highlight the syntax, but I'll add a note saying …