General

Profile

myronmarston (Myron Marston)

Issues

Activity

08/27/2015

07:53 PM Ruby trunk Feature #11491: Add descriptive methods to Method & UnboundMethod
I think that `Method#instance_method?` and `UnboundMethod#instance_method?` would be very confusing, because my menta...

05/04/2015

06:37 PM Ruby trunk Bug #11113: Time ranges cannot be used in case statements in 1.9+ but they could in 1.8.7
Thanks for the prompt fix, @nobu!!
On a side note, I wasn't notified by email of your fix even though I'm watching...

05/01/2015

10:56 PM Ruby trunk Bug #11113: Time ranges cannot be used in case statements in 1.9+ but they could in 1.8.7
> The "can't iterate" error is simply because Time is float-based: there is no succ number.
Floats don't have a `s...
03:15 PM Ruby trunk Bug #11113 (Closed): Time ranges cannot be used in case statements in 1.9+ but they could in 1.8.7
Given this script:
```ruby
range = (Time.now - 1000)...(Time.now + 1000)
case Time.now
when range then puts "...

04/15/2015

03:26 PM Ruby trunk Bug #11071: Stack consistency error while using RSpec and Timecop
There are two interesting things I've noticed about this:
1. It does not happen on 2.1, so it appears to be a regr...

12/31/2014

08:04 AM Ruby trunk Bug #10661: The "possible reference to past scope" warning is quite frustrating and is forcing me to change my variable names from what I want
Thank you, @nobu!

12/30/2014

04:21 AM Ruby trunk Bug #10661: The "possible reference to past scope" warning is quite frustrating and is forcing me to change my variable names from what I want
I'm also seeing this warning from rubygems in the ruby-head builds on travis:
```
/home/travis/.rvm/rubies/ruby-h...

12/27/2014

05:46 PM Ruby trunk Bug #10661: The "possible reference to past scope" warning is quite frustrating and is forcing me to change my variable names from what I want
> You can use `rand()`.
Good point. I'm so used to calling arg-less methods without parens that I didn't even thi...
09:14 AM Ruby trunk Bug #10661 (Closed): The "possible reference to past scope" warning is quite frustrating and is forcing me to change my variable names from what I want
I find the change in r48986 to be quite frustrating. It's forcing me to change many of my variable and/or method nam...

09/12/2014

06:47 AM Ruby trunk Bug #8982: NoMethodError#message produces surprising output when #inspect is defined on an anonymous class
So I've run into this issue again, and as it turns out, this is a much more widespread problem than I first thought. ...

Also available in: Atom