This project is archived and is in readonly mode.
Range#step parameter default (n=1) conflict
Reported by Brad Folkens | July 10th, 2008 @ 05:54 PM | in 2.1.1
ActiveSupport's step_with_blockless overrides Range#step(n=1) from Ruby's core and doesn't define the same n=1 default. This breaks Range#step when called without a parameter.
Is this intended? (If not, patch is attached)
ActiveSupport tests still pass with this patch.
Comments and changes to this ticket
-
Pratik July 14th, 2008 @ 01:16 AM
- Assigned user set to “Jeremy Kemper”
- Tag changed from “activesupport” to “activesupport, patch”
-
Jeremy Kemper August 28th, 2008 @ 07:48 AM
- State changed from “new” to “open”
- Milestone changed from “2.x” to “2.1.1”
-
Repository August 28th, 2008 @ 08:04 PM
- State changed from “open” to “resolved”
(from [b0907153da7b8bc8c02692eaadfac3a0853c0e99]) Reinstate Range#step default argument.
[#595 state:resolved]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net http://github.com/rails/rails/co...
-
Repository August 28th, 2008 @ 08:04 PM
(from [293f99700d6f2388ea5c504d706651ff3044d733]) Reinstate Range#step default argument.
[#595 state:resolved]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net http://github.com/rails/rails/co...
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Brad Folkens
Jeremy Kemper
Pratik
Attachments
Tags
Referenced by
-
595
Range#step parameter default (n=1) conflict
[#595 state:resolved]
-
595
Range#step parameter default (n=1) conflict
[#595 state:resolved]