[#113756] [Ruby master Bug#19711] NoMethodError "private method `new' called for class" since bebd05fb51ea65bc57344b67100748200f8311eb — "yahonda (Yasuo Honda) via ruby-core" <ruby-core@...>

Issue #19711 has been reported by yahonda (Yasuo Honda).

7 messages 2023/06/05

[#113771] [Ruby master Feature#19712] IO#reopen removes singleton class — "itarato (Peter Arato) via ruby-core" <ruby-core@...>

Issue #19712 has been reported by itarato (Peter Arato).

11 messages 2023/06/05

[#113782] [Ruby master Bug#19716] SystemStackError occurs too easily on Alpine Linux (due to small stack size reported by pthread_attr_getstacksize on musl libc) — "alexdowad (Alex Dowad) via ruby-core" <ruby-core@...>

Issue #19716 has been reported by alexdowad (Alex Dowad).

6 messages 2023/06/07

[#113788] [Ruby master Bug#19717] `ConditionVariable#signal` is not fair when the wakeup is consistently spurious. — "ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>

Issue #19717 has been reported by ioquatix (Samuel Williams).

13 messages 2023/06/07

[#113819] [Ruby master Feature#19720] Warning for non-linear Regexps — "Eregon (Benoit Daloze) via ruby-core" <ruby-core@...>

Issue #19720 has been reported by Eregon (Benoit Daloze).

11 messages 2023/06/08

[#113835] [Ruby master Misc#19722] DevMeeting-2023-07-13 — "mame (Yusuke Endoh) via ruby-core" <ruby-core@...>

Issue #19722 has been reported by mame (Yusuke Endoh).

9 messages 2023/06/09

[#113944] [Ruby master Feature#19737] Add `IO::Buffer#cat` for concat `IO::Buffer` instances — "unasuke (Yusuke Nakamura) via ruby-core" <ruby-core@...>

Issue #19737 has been reported by unasuke (Yusuke Nakamura).

7 messages 2023/06/19

[#113953] [Ruby master Bug#19739] Key cannot be found in a Hash when slice! method is applied to the key — "ilya.andreyuk (Ilya Andreyuk) via ruby-core" <ruby-core@...>

Issue #19739 has been reported by ilya.andreyuk (Ilya Andreyuk).

9 messages 2023/06/20

[#113966] [Ruby master Bug#19742] Introduce `Module#anonymous?` — "ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>

Issue #19742 has been reported by ioquatix (Samuel Williams).

47 messages 2023/06/21

[#114025] [Ruby master Feature#19744] Namespace on read — "tagomoris (Satoshi TAGOMORI) via ruby-core" <ruby-core@...>

Issue #19744 has been reported by tagomoris (Satoshi TAGOMORI).

71 messages 2023/06/27

[#114032] [Ruby master Misc#19747] Propose Kevin Newton and Jemma Issroff as core committers — "k0kubun (Takashi Kokubun) via ruby-core" <ruby-core@...>

Issue #19747 has been reported by k0kubun (Takashi Kokubun).

8 messages 2023/06/28

[#114038] [Ruby master Bug#19749] Confirm correct behaviour when attaching private method with `#define_method` — "itarato (Peter Arato) via ruby-core" <ruby-core@...>

Issue #19749 has been reported by itarato (Peter Arato).

15 messages 2023/06/28

[ruby-core:113916] [Ruby master Bug#19733] Kernel#Rational does not accept prefix 0

From: "sawa (Tsuyoshi Sawada) via ruby-core" <ruby-core@...>
Date: 2023-06-15 13:12:26 UTC
List: ruby-core #113916
Issue #19733 has been updated by sawa (Tsuyoshi Sawada).


@mame It seems that you were not aware of the fact that the documentation is wrong. And I hope you share with me the idea that we want the documentation to be correct. I think the reason why the documentation was wrong, and why you have not noticed it, is either because the specification is ad hoc or it was not implemented in the way it was intended. I believe this has to be solved in some way.

I can say that the current behavior is counter-intuitive. Even though `Integer` class is not a subclass of `Rational` class, coercion relation indicates that whatever can be interpreted as an `Integer` can be interpreted as a `Rational` but not vice versa. And I think people would normally expect whatever is interpretable by `Kernel#Integer` is interpretable by `Kernel#Rational`.

A use case that I can think of where this becomes relevant is an arithmetic program in which some string (from user input or from some data) is attempted to be interpreted using methods like `Kernel#Rational` or `Kernel#Integer` one after another (avoiding the use of methods like `eval` in fear of malicious code). Such program may attempt interpretation of a string by `Kernel#Rational`, and if it succeeds, go on to attempt interpretation by `Kernel#Integer` to see if the interpretation can be further narrowed down. However, if a non-decimal integer string is passed to `Kernel#Rational` and an error is raised, such program would give up attempting interpretation by `Kernel#Integer`, even though it would succeed, and that input string would be thrown away.


Even more strange is the fact that, in case of hexadecimal `0x` (but not with other `0` prefixes), it becomes interpretable by `Kernel#Float` again. This is a real mess.

```ruby
Integer("0x10") # => 2
Rational("0x10") # !> ArgumentError
Float("0x10") # => 10.0
```


----------------------------------------
Bug #19733: Kernel#Rational does not accept prefix 0
https://bugs.ruby-lang.org/issues/19733#change-103568

* Author: sawa (Tsuyoshi Sawada)
* Status: Feedback
* Priority: Normal
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
----------------------------------------
`Integer` and `Rational` literals accept prefix `0`. There is no difference in this respect.

```ruby
0b10 # => 2
0b10r # => (2/1)
```

However, when it comes to `Kernel#Integer` and `Kernel#Rational`, the former accepts prefix `0` while the latter does not. This is confusing. And as I do not see any reason they should behave differently, I think it is a bug. 

```ruby
Integer("0b10") # => 2
Rational("0b10") # !> ArgumentError
```



-- 
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/

In This Thread

Prev Next