[Issue 8839] MmFile do not use Range

2019-10-18 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=8839 berni44 changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 8839] MmFile do not use Range

2012-10-30 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8839 --- Comment #7 from bioinfornatics bioinfornat...@gmail.com 2012-10-30 16:05:44 PDT --- Since slicing use void[] as return type instead ubyte you can't use UFCS you need to cast it length member should be maybe size_t i think design this

[Issue 8839] MmFile do not use Range

2012-10-30 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8839 --- Comment #9 from bioinfornatics bioinfornat...@gmail.com 2012-10-30 16:26:08 PDT --- about breaking change i understand is important to D to get an api more stable about ufcs: - do not works _file[_currentPosition .. _file.length]

[Issue 8839] MmFile do not use Range

2012-10-30 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8839 --- Comment #10 from Jonathan M Davis jmdavisp...@gmx.com 2012-10-30 16:31:46 PDT --- Then save the range as a variable and use UFCS on that, or this would probably work: (cast(ubyte[])_file[_currentPosition .. _file.length]).countUntil!(a =

[Issue 8839] MmFile do not use Range

2012-10-30 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8839 --- Comment #11 from bioinfornatics bioinfornat...@gmail.com 2012-10-30 16:40:25 PDT --- for me that is ok but for new developer it could be little confused since in first it will try the common ufcs approach. It will get a strange template

[Issue 8839] MmFile do not use Range

2012-10-23 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8839 --- Comment #6 from bioinfornatics bioinfornat...@gmail.com 2012-10-23 12:19:39 PDT --- i totally agree with you now :-) but one day it will good to switch Mmfile to struct that is not huge break -- Configure issuemail:

[Issue 8839] MmFile do not use Range

2012-10-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8839 --- Comment #4 from bioinfornatics bioinfornat...@gmail.com 2012-10-18 15:31:12 PDT --- I mean a Phobos range as InputRange: requires the empty, front and popFront() member functions more info here: http://ddili.org/ders/d.en/ranges.html so

[Issue 8839] MmFile do not use Range

2012-10-18 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8839 --- Comment #5 from Jonathan M Davis jmdavisp...@gmx.com 2012-10-18 16:14:42 PDT --- I mean a Phobos range as InputRange: requires the empty, front and popFront() member functions Yeah. And arrays have that via std.array.empty,

[Issue 8839] MmFile do not use Range

2012-10-17 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8839 Jonathan M Davis jmdavisp...@gmx.com changed: What|Removed |Added CC|

[Issue 8839] MmFile do not use Range

2012-10-17 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8839 --- Comment #2 from bioinfornatics bioinfornat...@gmail.com 2012-10-17 15:48:54 PDT --- yes but it use opSlice method to do this not - front back safe … In more why it is a class instead a struct ? MmFile do not use inheritance --

[Issue 8839] MmFile do not use Range

2012-10-17 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8839 --- Comment #3 from Jonathan M Davis jmdavisp...@gmx.com 2012-10-17 16:41:29 PDT --- yes but it use opSlice method to do this not - front back safe … I don't know what you mean. In more why it is a class instead a struct ? MmFile do not