subject:"\[Issue 6730\] std.algorithm.splitter conflicts with std.array.splitter"

[Issue 6730] std.algorithm.splitter conflicts with std.array.splitter

2013-12-31 Thread d-bugmail

https://d.puremagic.com/issues/show_bug.cgi?id=6730 Walter Bright changed: What|Removed |Added CC||andrej.mitrov...@gmail.com --- Commen

[Issue 6730] std.algorithm.splitter conflicts with std.array.splitter

2013-12-29 Thread d-bugmail

https://d.puremagic.com/issues/show_bug.cgi?id=6730 --- Comment #8 from github-bugzi...@puremagic.com 2013-12-29 20:01:17 PST --- Commits pushed to master at https://github.com/D-Programming-Language/phobos https://github.com/D-Programming-Language/phobos/commit/06352bc88fc2a062ca25ef445c585235

[Issue 6730] std.algorithm.splitter conflicts with std.array.splitter

2013-12-29 Thread d-bugmail

https://d.puremagic.com/issues/show_bug.cgi?id=6730 Walter Bright changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

[Issue 6730] std.algorithm.splitter conflicts with std.array.splitter

2013-12-29 Thread d-bugmail

https://d.puremagic.com/issues/show_bug.cgi?id=6730 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment

[Issue 6730] std.algorithm.splitter conflicts with std.array.splitter

2013-10-03 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=6730 --- Comment #6 from monarchdo...@gmail.com 2013-10-03 00:24:49 PDT --- (In reply to comment #5) > Thing are really bad here as `std.range` which is often imported with > `std.algorithm` publicly imports `std.array` so this will fail to compile:

[Issue 6730] std.algorithm.splitter conflicts with std.array.splitter

2013-10-02 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=6730 Denis Shelomovskij changed: What|Removed |Added CC||verylonglogin@gmail.com

[Issue 6730] std.algorithm.splitter conflicts with std.array.splitter

2013-08-22 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=6730 monarchdo...@gmail.com changed: What|Removed |Added CC||dmitry.o...@gmail.com --- Comm

[Issue 6730] std.algorithm.splitter conflicts with std.array.splitter

2012-10-22 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=6730 --- Comment #3 from Jonathan M Davis 2012-10-22 23:16:16 PDT --- I find it highly unlikely that they'd be using it by mistake, but since it's undocumented, it's not unreasonable to break code that's using it. However, it's probably still bette

[Issue 6730] std.algorithm.splitter conflicts with std.array.splitter

2012-10-22 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=6730 --- Comment #2 from monarchdo...@gmail.com 2012-10-22 23:09:27 PDT --- (In reply to comment #1) > In general, I'd say yes. The fact that two functions in different modules can > have the same name and conflict is fully expected and acceptable. T