[Issue 5550] std.range.enumerate()

[d-bugmail at puremagic.com]

https://d.puremagic.com/issues/show_bug.cgi?id=5550



--- Comment #14 from bearophile_hugs at eml.cc 2014-01-17 01:59:48 PST ---
(In reply to comment #13)

> As far as I can tell, this cannot be implemented; it is an error that the
> compiler accepts use of `ref` in foreach over a range that doesn't have
> assignable elements. It is a problem shared with many other higher order
> ranges.

I see. Instead of disallowing this quite useful feature, are there plans to
improve the language to allow this feature in library code?


> I would also change [1 .. $] to .drop(1), but it is a minor stylistic issue.

Yes, in my code in a situation like that I'd like to use .dropOne, but I have
used a simpler slicing because it's "simpler", it doesn't introduce more ranges
from Phobos :-) When you explain one function in the documentation, you want to
minimize the number of other functions used.


> Also, to be a documented unittest, it needs to use assertions instead of pipe
> I/O.

Yeah.


> I still recommend you post on Github, it's likely that it will get more review
> and comments there. Also, it's only right that implementation comments go to
> the implementation proposed on Github, with the issue tracker dedicated to the
> problem statement in general...

>From my limited experience in commenting on GitHub, I've seen that currently
the linear threads in those GitHub pages are even less handy than the linear
threads here in Bugzilla, especially when the comments become longer than 2-3
lines of normal text. Here you can also add attaches.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------