[#46049] [ruby-trunk - Feature #6590] Dealing with bigdecimal, etc gems in JRuby — "mrkn (Kenta Murata)" <muraken@...>
4 messages
2012/07/01
[#46078] [ruby-trunk - Feature #2565] adding hooks for better tracing — "mame (Yusuke Endoh)" <mame@...>
4 messages
2012/07/01
[#46108] Re: [ruby-trunk - Feature #2565] adding hooks for better tracing
— Aaron Patterson <tenderlove@...>
2012/07/02
On Mon, Jul 02, 2012 at 03:06:59AM +0900, mame (Yusuke Endoh) wrote:
[#46127] [ruby-trunk - Feature #2565] adding hooks for better tracing — "vo.x (Vit Ondruch)" <v.ondruch@...>
4 messages
2012/07/03
[#46160] [ruby-trunk - Feature #6693][Open] Don't warn for unused variables starting with _ — "marcandre (Marc-Andre Lafortune)" <ruby-core@...>
15 messages
2012/07/04
[#46163] [ruby-trunk - Feature #6695][Open] Configuration for Thread/Fiber creation — "ko1 (Koichi Sasada)" <redmine@...>
7 messages
2012/07/04
[#46172] [ruby-trunk - Feature #6697][Open] [PATCH] Add Kernel#Symbol conversion method like String(), Array() etc. — "madeofcode (Mark Dodwell)" <mark@...>
7 messages
2012/07/04
[#46236] [ruby-trunk - Bug #6704][Open] Random core dump — "trans (Thomas Sawyer)" <transfire@...>
7 messages
2012/07/07
[#46248] building ruby-1.9.3-p194 on AIX 6.1 TL05 SP06 — Perry Smith <pedzsan@...>
I am just now starting to debug this but hoped someone has already =
10 messages
2012/07/08
[#46251] Re: building ruby-1.9.3-p194 on AIX 6.1 TL05 SP06
— Yutaka Kanemoto <kinpoco@...>
2012/07/08
Hi Perry
[#46252] Re: building ruby-1.9.3-p194 on AIX 6.1 TL05 SP06
— Perry Smith <pedzsan@...>
2012/07/08
[#46254] Re: building ruby-1.9.3-p194 on AIX 6.1 TL05 SP06
— Perry Smith <pedzsan@...>
2012/07/08
[#46259] Re: building ruby-1.9.3-p194 on AIX 6.1 TL05 SP06
— Perry Smith <pedzsan@...>
2012/07/09
[#46266] Re: building ruby-1.9.3-p194 on AIX 6.1 TL05 SP06
— Yutaka Kanemoto <kinpoco@...>
2012/07/09
Hi Perry,
[#46262] [ruby-trunk - Feature #6710][Open] new special binding specifier :isolated — "ko1 (Koichi Sasada)" <redmine@...>
8 messages
2012/07/09
[#46276] Lambdaification of Method Calls — Robert Klemme <shortcutter@...>
Hi,
3 messages
2012/07/09
[#46320] [ruby-trunk - Feature #6721][Open] Object#yield_self — "alexeymuranov (Alexey Muranov)" <redmine@...>
25 messages
2012/07/11
[#46339] [ruby-trunk - Bug #6724][Open] waaaaaaant! ( — "zenspider (Ryan Davis)" <redmine@...>
11 messages
2012/07/11
[#46537] Re: [ruby-trunk - Bug #6724][Open] waaaaaaant! (
— Aaron Patterson <tenderlove@...>
2012/07/17
On Thu, Jul 12, 2012 at 08:58:36AM +0900, zenspider (Ryan Davis) wrote:
[#46540] Re: [ruby-trunk - Bug #6724][Open] waaaaaaant! (
— Luis Lavena <luislavena@...>
2012/07/18
On Tue, Jul 17, 2012 at 6:27 PM, Aaron Patterson
[#46377] [ruby-trunk - Feature #6727][Open] Add Array#rest (with implementation) — "duckinator (Nick Markwell)" <nick@...>
25 messages
2012/07/13
[#46420] [ruby-trunk - Feature #6731][Open] add new method "Object.present?" as a counter to #empty? — "rogerdpack (Roger Pack)" <rogerpack2005@...>
4 messages
2012/07/14
[#46500] [ruby-trunk - Feature #6739][Open] One-line rescue statement should support specifying an exception class — Quintus (Marvin Gülker) <sutniuq@...>
22 messages
2012/07/15
[#46535] [ruby-trunk - Bug #6749][Open] rdoc of Time class (incorrect explanation of leap seconds) — "stomar (Marcus Stollsteimer)" <redmine@...>
7 messages
2012/07/17
[#46687] [ruby-trunk - Bug #6749] rdoc of Time class (incorrect explanation of leap seconds)
— "drbrain (Eric Hodel)" <[email protected]>
2012/07/23
[#46713] Re: [ruby-trunk - Bug #6749] rdoc of Time class (incorrect explanation of leap seconds)
— sto.mar@...
2012/07/24
Hi Eric,
[#46734] Re: [ruby-trunk - Bug #6749] rdoc of Time class (incorrect explanation of leap seconds)
— Eric Hodel <[email protected]>
2012/07/24
On Jul 23, 2012, at 11:52 PM, [email protected] wrote:
[#46763] Re: [ruby-trunk - Bug #6749] rdoc of Time class (incorrect explanation of leap seconds)
— sto.mar@...
2012/07/25
Am 24.07.2012 19:44, schrieb Eric Hodel:
[#46546] Fwd: [ruby-cvs:43609] ko1:r36433 (trunk): * thread.c (rb_thread_call_without_gvl2): added. — SASADA Koichi <ko1@...>
Hi,
4 messages
2012/07/18
[#46547] Re: Fwd: [ruby-cvs:43609] ko1:r36433 (trunk): * thread.c (rb_thread_call_without_gvl2): added.
— Eric Wong <normalperson@...>
2012/07/18
SASADA Koichi <[email protected]> wrote:
[#46553] [ruby-trunk - Feature #2565] adding hooks for better tracing — "tenderlovemaking (Aaron Patterson)" <aaron@...>
4 messages
2012/07/18
[#46564] Ruby under CI - Windows — Luis Lavena <luislavena@...>
Hello,
6 messages
2012/07/20
[#46574] [ruby-trunk - Feature #6762][Open] Control interrupt timing — "ko1 (Koichi Sasada)" <redmine@...>
39 messages
2012/07/20
[#46575] [ruby-trunk - Feature #6762] Control interrupt timing
— "ko1 (Koichi Sasada)" <redmine@...>
2012/07/20
[#50542] Re: [ruby-trunk - Feature #6762][Open] Control interrupt timing
— Brent Roman <brent@...>
2012/12/03
I was suggesting "interruptible" as a better alternative for
[#46577] [ruby-trunk - Feature #6763][Open] Introduce Flonum technique to speedup floating computation on th 64bit environment — "ko1 (Koichi Sasada)" <redmine@...>
7 messages
2012/07/20
[#46586] [ruby-trunk - Bug #6764][Open] IO#read(size, buf) causes can't set length of shared string in trunk (2.0.0dev) — "nahi (Hiroshi Nakamura)" <nakahiro@...>
4 messages
2012/07/21
[#46641] [ruby-trunk - Bug #6780][Open] cannot compile zlib module, when cross-compiling. — "jinleileiking (lei king)" <jinleileiking@...>
14 messages
2012/07/23
[#46686] [ruby-trunk - Bug #6784][Open] Test failures related to numeric with x64 mingw — "h.shirosaki (Hiroshi Shirosaki)" <h.shirosaki@...>
5 messages
2012/07/23
[#46741] [ruby-trunk - Bug #6789][Open] parse.y compilation error due not updated id.h — "luislavena (Luis Lavena)" <luislavena@...>
8 messages
2012/07/24
[#46742] [ruby-trunk - Bug #6789][Assigned] parse.y compilation error due not updated id.h
— "luislavena (Luis Lavena)" <luislavena@...>
2012/07/24
[#46744] [ruby-trunk - Bug #6791][Open] ext/js on/generator/generator.c fails to compile on nightly build (AIX 6.1) — "pedz (Perry Smith)" <pedz@...>
4 messages
2012/07/25
[#46752] Re: [ruby-trunk - Bug #6791][Open] ext/js on/generator/generator.c fails to compile on nightly build (AIX 6.1)
— Yutaka Kanemoto <kinpoco@...>
2012/07/25
Hi Perry,
[#46772] Ruby 1.9.3 release? — Charles Oliver Nutter <headius@...>
JRuby will soon release 1.7.0pre2, the second preview of 1.7. Perhaps
6 messages
2012/07/25
[#46847] Re: Ruby 1.9.3 release?
— "NARUSE, Yui" <naruse@...>
2012/07/29
(2012/07/26 7:07), Charles Oliver Nutter wrote:
[#46864] Re: Ruby 1.9.3 release?
— Luis Lavena <luislavena@...>
2012/07/29
On Sat, Jul 28, 2012 at 10:59 PM, NARUSE, Yui <[email protected]> wrote:
[#46792] [ruby-trunk - Bug #6799][Open] Digest::*.hexdigest returns an ASCII-8BIT String — "Eregon (Benoit Daloze)" <redmine@...>
11 messages
2012/07/26
[#46832] [ruby-trunk - Bug #6807][Open] Can't compile ruby without ruby — "devcurmudgeon (Paul Sherwood)" <storitel@...>
13 messages
2012/07/28
[#46834] [ruby-trunk - Feature #6808][Open] Implicit index for enumerations — "trans (Thomas Sawyer)" <transfire@...>
15 messages
2012/07/28
[#46838] [ruby-trunk - Bug #6810][Open] `module A::B; end` is not equivalent to `module A; module B; end; end` with respect to constant lookup (scope) — "alexeymuranov (Alexey Muranov)" <redmine@...>
17 messages
2012/07/28
[#46854] [ruby-trunk - Feature #6811][Open] File, Dir and FileUtils should have bang-versions of singleton methods that fails silently — "prijutme4ty (Ilya Vorontsov)" <prijutme4ty@...>
7 messages
2012/07/29
[#46896] (Half-baked DRAFT) new `require' framework — SASADA Koichi <ko1@...>
Hi,
22 messages
2012/07/31
[#46897] Re: (Half-baked DRAFT) new `require' framework
— =?KOI8-R?B?4NLJyiDzz8vPzM/X?= <funny.falcon@...>
2012/07/31
2012/7/31 SASADA Koichi <[email protected]>
[#46899] Re: (Half-baked DRAFT) new `require' framework
— Alex Young <alex@...>
2012/07/31
On 31/07/12 13:29, SASADA Koichi wrote:
[#46902] Re: (Half-baked DRAFT) new `require' framework
— Trans <transfire@...>
2012/07/31
On Tue, Jul 31, 2012 at 12:07 PM, Alex Young <[email protected]> wrote:
[#46903] Re: (Half-baked DRAFT) new `require' framework
— Clifford Heath <clifford.heath@...>
2012/07/31
On 01/08/2012, at 5:59 AM, Trans wrote:
[#47040] Re: (Half-baked DRAFT) new `require' framework
— SASADA Koichi <ko1@...>
2012/08/07
(2012/07/31 21:29), SASADA Koichi wrote:
[#47054] Re: (Half-baked DRAFT) new `require' framework
— Rocky Bernstein <rockyb@...>
2012/08/07
If one is considering importing archive files like zip, tar, jar, or gem, I
[#47056] Re: (Half-baked DRAFT) new `require' framework
— Charles Oliver Nutter <headius@...>
2012/08/07
On Tue, Aug 7, 2012 at 8:48 AM, Rocky Bernstein <[email protected]> wrote:
[ruby-core:46338] [ruby-trunk - Feature #6688] Object#replace
From:
"prijutme4ty (Ilya Vorontsov)" <prijutme4ty@...>
Date:
2012-07-11 23:24:49 UTC
List:
ruby-core #46338
Issue #6688 has been updated by prijutme4ty (Ilya Vorontsov).
trans (Thomas Sawyer) wrote:
> =begin
> I don't think #replace works on Enumerables, rather it works on Array and Hash.
>
> It does seem a rather powerful notion to be able to replace an object with another wherever is may be referenced. Though @shudo may be right that it is too dangerous. With good design, a proper interface can handle the reassignment through the usual mechanisms, although admittedly it may entail many more compute cycles to do it.
>
> On the other hand, if Smalltalk supports it then perhaps it's worth consideration. Always respect the Smalltalk :) But I agree with it, better name is #become.
>
> Also note that a less dangerous notion of a generic replace is simply to copy common instance variables.
>
> class X
> def initialize(a)
> @a = a
> end
> end
>
> class Y
> def initialize(a,b)
> @a, @b = a, b
> end
> end
>
> x = X.new(1)
> y = Y.new(2,3)
>
> x.a #=> 1
> x.replace(y)
> x.a #=> 2
>
> Although a more appropriate name for this is probably #instance_replace. This preserves object identity, but can only be used to "copy" an object of the same type --which, if you think about it, is what Array#replace and Hash#replace does too actually.
> =end
Object copying is useful but far less powerful. Imagine that you want to redefine files ARGF is linked to. Instead of
ARGV = ['filename','filename2']; puts ARGF
you should write
ARGV.replace ['filename','filename2']; puts ARGF
But now imagine that you want to use lazy enumerator to print content of all files in a directory. You don't want to create an array of all files, so you just try to write
`ARGV.replace Dir.to_enum(:glob,'**/*.txt'); puts ARGF`
...and fails because you can't use enumerable here, only an array. Why we should put up with it if it can be improved not to break duck-typing paradigm?
----------------------------------------
Feature #6688: Object#replace
https://bugs.ruby-lang.org/issues/6688#change-27955
Author: prijutme4ty (Ilya Vorontsov)
Status: Open
Priority: Normal
Assignee:
Category:
Target version:
I suggest that #replace works not only on Enumerables but on any Object. It can make use the same object in different places more consistent. It makes it possible to write
class Egg; end
class Hen; end
class HenHouse; attr_accessor :species; end
class Incubator; def incubate(egg) Hen.new; end
# Here it is!
class IncubatorWithReplace;
def incubate(egg)
egg.replace(Hen.new)
end
end
e1,e2,e3 = Egg.new, Egg.new, Egg.new
h1, h2 = HenHouse.new, HenHouse.new
# One egg is shared between hen houses
h1.species = [e1, e2]
h2.species = [e1, e3]
p h1 # ==> <HenHouse @species = [#<Egg 1>,#<Egg 2>]
p h2 # ==> <HenHouse @species = [#<Egg 1>,#<Egg 3>]
# First option. It's bad choise because it makes two "data structures" HenHouse inconsistent:
# they have different object while must have the same
h1[0] = Incubator.new.incubate(h1[0])
p h1 # ==> <HenHouse @species = [#<Hen>,#<Egg 2>]
p h2 # ==> <HenHouse @species = [#<Egg 1>,#<Egg 3>]
# Second option is ok - now both shared objects're changed.
IncubatorWithReplace.new.incubate(h1[0])
h1 # ==> <HenHouse @species = [#<Hen>,#<Egg 2>]
h2 # ==> <HenHouse @species = [#<Hen>,#<Egg 3>]
# Third option is bad - it wouldn't affect HenHouses at all
e1 = Incubator.new.incubate(e1)
p h1 # ==> <HenHouse @species = [#<Egg 1>,#<Egg 2>]
p h2 # ==> <HenHouse @species = [#<Egg 1>,#<Egg 3>]
# while Fourth option is ok and works as second do
IncubatorWithReplace.new.incubate(e1) ## would affect both HenHouses
p h1 # ==> <HenHouse @species = [#<Hen>,#<Egg 2>]
p h2 # ==> <HenHouse @species = [#<Egg 1>,#<Egg 3>]
I can't imagine how it'd be realized, it looks like some dark magic with ObjectSpace needed to replace one object at a reference with another at the same reference. But I didn't found a solution.
About ret-value. I think it should be two forms:
Object#replace(obj, retain = false)
If retain is false #replace should return a reference to a new object (in fact the same reference as to old object but with other content)
If retain is true, old object should be moved at another place and new reference to it is returned, so:
e1 # ==> <Egg id:1>
e1.replace( Hen.new, true ) # ==> <Egg id:2>
e1 # ==> <Hen id:1>
--
http://bugs.ruby-lang.org/