Twitter | Search | |
Dan Luu 30 Sep 17
Replying to @danluu
Apparently some Ruby methods can't be overridden because they're hardcoded in C for some implementations?
Reply Retweet Like
Noah Gibbs 2 Oct 17
Replying to @schneems @danluu
I'd call it "technically a bug" - she's right, it's an odd behavior. Though yeah, it's a (very) slight over-optimization.
Reply Retweet Like
Dan Luu 2 Oct 17
Replying to @codefolio @schneems
I'm curious what the perf cost of fast path in C w/ check for slow override path would be. My guess would be that it's nearly free.
Reply Retweet Like
Dan Luu 2 Oct 17
Replying to @codefolio @schneems
Adding integer overflow checks in C is ~1%. I'd expect Ruby to be slow enough that the analogous checking in C impl wouldn't be noticable?
Reply Retweet Like
Dan Luu 2 Oct 17
Replying to @codefolio @schneems
I don't know Ruby, so maybe that's totally wrong, but it should be pretty easy to check despite not knowing Ruby...
Reply Retweet Like
Dan Luu 11 Oct 17
Replying to @danluu
Every post on this blog a delightful exploration 😄
Reply Retweet Like