< :前の番号
^ :番号順リスト
> :次の番号
P :前の記事(スレッド移動)
N :次の記事(スレッド移動)
|<:前のスレッド
>|:次のスレッド
^ :返事先
_:自分への返事
>:同じ返事先を持つ記事(前)
<:同じ返事先を持つ記事(後)
---:分割してスレッド表示、再表示
| :分割して(縦)スレッド表示、再表示
~ :スレッドのフレーム消去
.:インデックス
..:インデックスのインデックス
Issue #7848 has been updated by ko1 (Koichi Sasada).
Category set to core
Assignee set to matz (Yukihiro Matsumoto)
Target version set to next minor
I don't think this proposal can be accepted.
----------------------------------------
Feature #7848: Restore default state for core ruby objects
https://bugs.ruby-lang.org/issues/7848#change-36370
Author: shevegen (markus heiler)
Status: Open
Priority: Low
Assignee: matz (Yukihiro Matsumoto)
Category: core
Target version: next minor
Hi.
Consider:
class String
def lala
puts 'Running lala() from class String.'
end
end
This is possible.
My question is - is there a reason why we can not restore
to the default ruby state again?
For instance, if I would do:
String.restore
I could undo all modifications to String, save what was used
in String class on startup/initialize.
The reason I would like to have something like this is so
that I could safely undo all "monkey" patches again, if needed,
for a given project.
--
http://bugs.ruby-lang.org/