Andreas Rumpf

> I'm a little late, but I wanted to +1 this. I'm wrapping the Ruby C API, and it would be great if existing code/books/tutorials could be used for reference...

Well you also didn't outline how these trailing/leading underscores effect the identifier equality rules, it's more rules to remember and worst of all: It's ugly. https://youtu.be/8v5CuyuS5wg?t=27 ;-) The underscore is...

That's not what your RFC says...

It's quite easily possible to change the language and to allow for more underscores. That's not why I'm against the feature. I'm against it because it's ugly. However, as a...

Well this is supposed to be an RFC, "see the issues linked elsewhere" doesn't suffice and the subset of the issues that I looked at didn't convince me.

I get: ``` ==1081== Invalid read of size 8 ==1081== at 0x113A54: system::markGray(ptr, ptr, var) (@[email protected]:1129) ==1081== by 0x112575: system::collectCyclesBacon(var, int) (@[email protected]:1427) ==1081== by 0x112B70: system::collectCycles (@[email protected]:1529) ==1081== by 0x113028:...

Interesting ideas but I fear the additional complexity.

I like it but maybe it should be under ``nim-lang/cairo2``?

@treeform But are surfaces the only exposed resource? The surface is only an example here.

> Will the =destroy only work with --gc:arc? No, it's always active, however the old seq implementation (and stuff building on top like tables) ignores destructors.