matsadler

6 ms·

1.
by matsadler 3y ago
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 stable set of 2D points to sample an image, and the
2.
by matsadler 4y ago
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] which is lower level bindings direct to the Ruby C API. [1]:
3.
by matsadler 4y ago
Add support for bundle gem --ext=rust command. Cool to see support for writing extension gems in Rust shipping with Ruby.
4.
by matsadler 4y ago
https://github.com/ankane/tokenizers-ruby
5.
by matsadler 4y ago
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 support, plus other improvements was a daunting task with t
6.
by matsadler 12y ago
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
7.
by matsadler 12y ago
For the cases I have benchmarked concatenation with << has been faster than join on an array. Here's a simple benchmark: require "benchmark" n = 100_000 Benchmark.bm(4) do |x| x.report("<&lt
8.
by matsadler 13y ago
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 young and old generations. A regular GC run will only lo
9.
by matsadler 13y ago
#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://globaldev.co.uk/2013/03/ruby-2-
10.
by matsadler 13y ago
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 `def foo( * )` is an alternative to having to na
11.
by matsadler 13y ago
(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 it's maybe not the best idea to actually use