Actions
Feature #17040
opencleanup include/ruby/backward*
Status:
Open
Assignee:
-
Target version:
-
Description
I recently noticed [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
- include/ruby/backward/classext.h: deprecated since 1.9.3. PR
- struct RClassDeprecated: deprecated since 2.3.0. PR
- include/ruby/backward/rubysig.h: deprecated since 1.9.0. PR
- include/ruby/backward/rubyio.h: deprecated since 1.9.0. PR
- include/ruby/backward/st.h: deprecated since 1.9.0. PR
- include/ruby/backward/util.h: deprecated since 1.9.0. PR
Updated by shyouhei (Shyouhei Urabe) over 4 years ago
I'm pretty confident that nobody is against such change. But opening an issue anyways, because this is a breaking change.
Updated by naruse (Yui NARUSE) about 4 years ago
It looks implementation detail and concurrent gems already supports new headers.
Go ahead
Actions
Like0
Like0Like0Like0Like0