[#99426] [Ruby master Bug#17098] Float#negative? reports negative zero as not negative — chris@...

Issue #17098 has been reported by chrisseaton (Chris Seaton).

12 messages 2020/08/01

[#99449] [Ruby master Bug#17100] Ractor: a proposal for new concurrent abstraction without thread-safety issues — ko1@...

Issue #17100 has been reported by ko1 (Koichi Sasada).

41 messages 2020/08/03

[#99474] [Ruby master Feature#17103] Add a :since option to ObjectSpace.dump_all — jean.boussier@...

Issue #17103 has been reported by byroot (Jean Boussier).

9 messages 2020/08/04

[#99485] [Ruby master Misc#17104] Why are interpolated string literals frozen? — bughitgithub@...

Issue #17104 has been reported by bughit (bug hit).

23 messages 2020/08/05

[#99499] [Ruby master Bug#17105] A single `return` can return to two different places in a proc inside a lambda inside a method — eregontp@...

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

10 messages 2020/08/06

[#99582] [Ruby master Feature#17122] Add category to Warning#warn — eileencodes@...

Issue #17122 has been reported by eileencodes (Eileen Uchitelle).

20 messages 2020/08/13

[#99700] [Ruby master Bug#17129] bundle install `eventmachine` and `sassc` fails since 914b2208ab3eddec478cdc3e079e6c30d0f0892c — yasuo.honda@...

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

9 messages 2020/08/26

[ruby-core:99697] [Ruby master Feature#17040] cleanup include/ruby/backward*

From: naruse@...
Date: 2020-08-26 07:07:26 UTC
List: ruby-core #99697
Issue #17040 has been updated by naruse (Yui NARUSE).


It looks implementation detail and concurrent gems already supports new headers.
Go ahead

----------------------------------------
Feature #17040: cleanup include/ruby/backward*
https://bugs.ruby-lang.org/issues/17040#change-87188

* Author: shyouhei (Shyouhei Urabe)
* Status: Open
* Priority: Normal
----------------------------------------
I recently noticed [[ruby-dev:35813]](http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-dev/35813):

> こんなところでどうでしょうか。include/ruby/backwardは2.0までには
> 削除するということで。

It reads: "How about the following.  Will delete include/ruby/backward by 2.0."

In reality, the directories lasted for the entire 2.x era.  But isn't 3.0 a good time to finally delete them?

- include/ruby/backward/2/extern.h: deprecated since 1.8.0. [PR](https://github.com/ruby/ruby/pull/3338)
- include/ruby/backward/classext.h: deprecated since 1.9.3. [PR](https://github.com/ruby/ruby/pull/3340)
    - struct RClassDeprecated: deprecated since 2.3.0. [PR](https://github.com/ruby/ruby/pull/3341)
- include/ruby/backward/rubysig.h: deprecated since 1.9.0. [PR](https://github.com/ruby/ruby/pull/3343)
- include/ruby/backward/rubyio.h: deprecated since 1.9.0. [PR](https://github.com/ruby/ruby/pull/3344)
- include/ruby/backward/st.h: deprecated since 1.9.0. [PR](https://github.com/ruby/ruby/pull/3345)
- include/ruby/backward/util.h: deprecated since 1.9.0. [PR](https://github.com/ruby/ruby/pull/3345)



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next