subject:"\[Issue 9582\] std.algorithm.map\!\(T\) cause CT error for fixed size arrays"

[Issue 9582] std.algorithm.map!(T) cause CT error for fixed size arrays

2020-03-20 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=9582 Basile-z changed: What|Removed |Added CC|b2.t...@gmx.com | --

[Issue 9582] std.algorithm.map!(T) cause CT error for fixed size arrays

2019-12-13 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=9582 berni44 changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 9582] std.algorithm.map!(T) cause CT error for fixed size arrays

2017-12-04 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=9582 Basile B. changed: What|Removed |Added CC||b2.t...@gmx.com Hardware|x86

[Issue 9582] std.algorithm.map!(T) cause CT error for fixed size arrays

2013-02-24 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=9582 --- Comment #11 from bearophile_h...@eml.cc 2013-02-24 16:11:10 PST --- (In reply to comment #10) > But the way I see it, your argument is that loop unrolling justifies copying > an > entire array. If your array is a ubyte[6] then I think cop

[Issue 9582] std.algorithm.map!(T) cause CT error for fixed size arrays

2013-02-24 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=9582 --- Comment #10 from monarchdo...@gmail.com 2013-02-24 15:41:59 PST --- (In reply to comment #9) > In the end I am probably able to add the missing [] to my D2 code in a matter > of one or two hours (or less) so for me this change doesn't requir

[Issue 9582] std.algorithm.map!(T) cause CT error for fixed size arrays

2013-02-24 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=9582 --- Comment #9 from bearophile_h...@eml.cc 2013-02-24 14:40:31 PST --- (In reply to comment #8) > Can you elaborate on the "why" though? Is it just because it would be > "breaking > change", or do you have a use case that warrants its being in

[Issue 9582] std.algorithm.map!(T) cause CT error for fixed size arrays

2013-02-24 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=9582 --- Comment #8 from monarchdo...@gmail.com 2013-02-24 13:59:12 PST --- (In reply to comment #7) > (In reply to comment #6) > > > I am strongly against this breaking change. > > Sorry, that came out too much strong... Don't worry about it, I d

[Issue 9582] std.algorithm.map!(T) cause CT error for fixed size arrays

2013-02-24 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=9582 --- Comment #7 from bearophile_h...@eml.cc 2013-02-24 13:49:05 PST --- (In reply to comment #6) > I am strongly against this breaking change. Sorry, that came out too much strong... -- Configure issuemail: http://d.puremagic.com/issues/userp

[Issue 9582] std.algorithm.map!(T) cause CT error for fixed size arrays

2013-02-24 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=9582 --- Comment #6 from bearophile_h...@eml.cc 2013-02-24 08:52:34 PST --- (In reply to comment #3) > As for reduce accepting iterable, Andrei asked me to remove it in one of my > open requests, so don't expect it keep working for too long. I am s

[Issue 9582] std.algorithm.map!(T) cause CT error for fixed size arrays

2013-02-24 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=9582 --- Comment #5 from monarchdo...@gmail.com 2013-02-24 08:21:49 PST --- (In reply to comment #4) > (In reply to comment #3) > > ...and this is good example of why accepting an "iterable" as a function > > argument, as opposed to a range, is usual

[Issue 9582] std.algorithm.map!(T) cause CT error for fixed size arrays

2013-02-24 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=9582 --- Comment #4 from Peter Alexander 2013-02-24 08:16:44 PST --- (In reply to comment #3) > ...and this is good example of why accepting an "iterable" as a function > argument, as opposed to a range, is usually a bad idea. > > As for reduce ac