[Issue 4572] std.file.read return type

https://issues.dlang.org/show_bug.cgi?id=4572 Andrei Alexandrescu changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Issue 4572] std.file.read return type

http://d.puremagic.com/issues/show_bug.cgi?id=4572 Andrei Alexandrescu and...@metalanguage.com changed: What|Removed |Added Status|NEW |ASSIGNED

[Issue 4572] std.file.read return type

http://d.puremagic.com/issues/show_bug.cgi?id=4572 --- Comment #12 from Sobirari Muhomori dfj1es...@sneakemail.com 2010-10-15 10:39:39 PDT --- To me void[] stinks a lot and it's not a big deal to avoid it completely. It's an abomination from trying to evolve C concepts for D. -- Configure

[Issue 4572] std.file.read return type

http://d.puremagic.com/issues/show_bug.cgi?id=4572 Steven Schveighoffer schvei...@yahoo.com changed: What|Removed |Added CC|

[Issue 4572] std.file.read return type

http://d.puremagic.com/issues/show_bug.cgi?id=4572 --- Comment #6 from bearophile_h...@eml.cc 2010-08-04 05:52:31 PDT --- Thank you for your answer Steven. then, you must cast your data to a ubyte[]. But void[] can be implicitly cast to from anything, so void[] wins here. If you compile

[Issue 4572] std.file.read return type

http://d.puremagic.com/issues/show_bug.cgi?id=4572 --- Comment #7 from Steven Schveighoffer schvei...@yahoo.com 2010-08-04 06:02:21 PDT --- (In reply to comment #6) Thank you for your answer Steven. then, you must cast your data to a ubyte[]. But void[] can be implicitly cast to

[Issue 4572] std.file.read return type

http://d.puremagic.com/issues/show_bug.cgi?id=4572 --- Comment #8 from bearophile_h...@eml.cc 2010-08-04 08:20:32 PDT --- Steven Schveighoffer: Well, I would assume it would return an int[][], which probably would mean nothing since arrays are pointer/length values, and any pointer/length

[Issue 4572] std.file.read return type

http://d.puremagic.com/issues/show_bug.cgi?id=4572 --- Comment #9 from nfx...@gmail.com 2010-08-04 09:23:45 PDT --- (In reply to comment #5) any array operation which copies a block to another copies the flags from the original array block. So the NO_SCAN flag should persist. If it doesn't,

[Issue 4572] std.file.read return type

http://d.puremagic.com/issues/show_bug.cgi?id=4572 --- Comment #10 from Steven Schveighoffer schvei...@yahoo.com 2010-08-04 10:31:17 PDT --- (In reply to comment #9) (In reply to comment #5) any array operation which copies a block to another copies the flags from the original array

[Issue 4572] std.file.read return type

http://d.puremagic.com/issues/show_bug.cgi?id=4572 David Simcha dsim...@yahoo.com changed: What|Removed |Added CC||dsim...@yahoo.com ---

[Issue 4572] std.file.read return type

http://d.puremagic.com/issues/show_bug.cgi?id=4572 nfx...@gmail.com changed: What|Removed |Added CC||nfx...@gmail.com --- Comment #2

[Issue 4572] std.file.read return type

http://d.puremagic.com/issues/show_bug.cgi?id=4572 --- Comment #3 from bearophile_h...@eml.cc 2010-08-03 09:09:48 PDT --- Thank you David and nfxjfg :-) -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---

[Issue 4572] std.file.read return type

http://d.puremagic.com/issues/show_bug.cgi?id=4572 --- Comment #4 from nfx...@gmail.com 2010-08-03 09:22:36 PDT --- One can add that .dup-ing a void[] will make all the precaution in std.file.read of allocating the void[] with GC.BlkAttr.NO_SCAN useless. The dup'ed array won't have the NO_SCAN