General

Profile

nelhage (Nelson Elhage)

  • Login: nelhage
  • Registered on: 04/04/2017
  • Last sign in: 08/13/2019

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 0 5 5

Activity

07/25/2019

09:01 PM Ruby Feature #15955: UnboundMethod#apply
Whoops, sorry for the belated response -- Redmine email seems to not be working for me. We have a `replace_method` helper that is a shorthand for doing something like:
```
orig_require = Kernel.instance_method(:require)
Kernel.defin...
nelhage (Nelson Elhage)

06/24/2019

05:49 PM Ruby Feature #15955 (Closed): UnboundMethod#apply
I'd love a way to apply an UnboundMethod to a receiver and list of args without having to first `bind` it. I've ended up using `UnboundMethod`s in some hot paths in my application due to our metaprogramming idioms, and the allocation fro... nelhage (Nelson Elhage)

05/02/2019

05:03 PM Ruby Feature #15818 (Rejected): Please hide ruby-doc.org pages for EOL releases from the Google index
It's a very common experience that if I google a Ruby method or class, the top Google link to me points to the docs for Ruby 2.2 or 2.1 or even 1.9 or 1.8. As a recent example, googling [ruby unicode_normalize] finds me https://ruby-doc.... nelhage (Nelson Elhage)

02/27/2019

05:36 PM Ruby Bug #15625 (Closed): Module#name performance has exponential-time worst case by aliased constants
It's well-known (c.f #11119) that `Module#name` has poor performance on anonymous classes, due to searching the entire constant namespace of the VM.
However, we recently discovered that it's even worse than that. In the presence of al...
nelhage (Nelson Elhage)

05/10/2018

11:41 PM Ruby Bug #14748 (Closed): Inconsistent (and regressed from 2.4) behavior on `Array#min` and max between array literals and arrays
`Array#min` and `Array#max` have different behavior depending on whether or not they are called with array literals:
~~~
$ ruby -e 'puts([1.0, 1].min); one_f = 1.0; one = 1; puts([one_f, one].min)'
1.0
1
~~~
This is a regress...
nelhage (Nelson Elhage)

12/20/2017

11:42 PM Ruby Bug #13305: Occasional segfaults after defining methods while running coverage
Can this fix be backported to the Ruby 2.4 release series? 2.4.3 is still affected by this crash. nelhage (Nelson Elhage)

04/05/2017

04:18 PM Ruby Bug #13404 (Rejected): Hash#any? yields arguments to lambdas with proc semantics
```
l = ->(a, b) { true }
# Raises; Uses Enumerable#all?
{1 => 2}.all?(&l)
# Does not raise; Uses specialized Hash#any?
{1 => 2}.any?(&l)
```
The `Enumerable` behavior was changed (correctly) in #12705, but the `Hash#any?` i...
nelhage (Nelson Elhage)

Also available in: Atom