From: "andrykonchin (Andrew Konchin)" <noreply@...>
Date: 2022-12-13T15:17:41+00:00
Subject: [ruby-core:111272] [Ruby master Bug#19231] Integer#step and Float::INFINITY - inconsistent behaviour when called with and without a block

Issue #19231 has been reported by andrykonchin (Andrew Konchin).

----------------------------------------
Bug #19231: Integer#step and Float::INFINITY - inconsistent behaviour when called with and without a block
https://bugs.ruby-lang.org/issues/19231

* Author: andrykonchin (Andrew Konchin)
* Status: Open
* Priority: Normal
* ruby -v: 3.1.2
* Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
The initial issue was reported here https://github.com/oracle/truffleruby/issues/2797.

`0.step(Float::INFINITY, 10)` returns:
- `Integers` when called with a block
- `Floats` when called without a block

I would expect `Floats` to be returned in both cases.

Examples:

```ruby
0.step(100.0, 10).take(1).map(&:class)
# => [Float]
```

```ruby
0.step(Float::INFINITY, 10) { |offset| p offset.class; break }
# Integer
```

When `to` argument is a finite `Float` value then calling with a block returns `Floats` as well:

```ruby
0.step(100.0, 10) { |offset| p offset.class; break }
# Float
```

Wondering whether it's intentional behaviour.

I've found a related issue https://bugs.ruby-lang.org/issues/15518.



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/