I unequivocally support this initiative. I have always known the Ruby community as a positive, diverse, and welcoming place. Adopting a Code of Conduct is merely a way of stating explicitly what kind of behavior is or isn't welcome. Good...plexus (Arne Brasseur)
That makes sense, I agree with your point. Having a nicer error message on broken code isn't a big deal. There is an actual use case beyond "a nicer error message" though. Me and others make heavy use of mutation testing with Mutan...plexus (Arne Brasseur)
Was it rude to set this as "Priority: High"? A random segfault seems important but it also seems very few tickets are actually marked as high priority.plexus (Arne Brasseur)
Did some more testing on current trunk (trunk@48266) Depending on the optimization level I get different results. -O0 works correctly, -O1 segfaults, -O2 works correctly, -O3 hangs. strace of the two problematic versions: * -O1...plexus (Arne Brasseur)
The code to trigger this can be found here: https://gist.github.com/mbj/31163a8e712573877268 Also have a look at the comments there. A lot of different people tried it, in some cases it segfaults, in others it doesn't. It seems to hav...plexus (Arne Brasseur)
Updated the patch with documentation. There's an interesting side effect to be considered. `Method#to_proc` returns a lambda that checks its arity. `Proc#curry` takes an optional `arity` argument. If this doesn't match the method's arity...plexus (Arne Brasseur)
There is already Proc#curry, but to curry a method you need to go through to_proc. This patch adds `Method#curry` which delegates to `method.to_proc.curry`. Looking forward to seeing this discussed.plexus (Arne Brasseur)
To make Pathname and URI more consistent, it would be great to have a `join` instance method that behaves like `Pathname#join`. This could be a simple alias of `URI#merge`.plexus (Arne Brasseur)