[Issue 6547] Call to std.algorithm.remove causes compile error
d-bugmail at puremagic.com
d-bugmail at puremagic.com
Tue Mar 13 15:39:35 PDT 2012
http://d.puremagic.com/issues/show_bug.cgi?id=6547
Tim Keating <itsallaboutthedyo at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #2 from Tim Keating <itsallaboutthedyo at gmail.com> 2012-03-13 15:39:44 PDT ---
I will say that I don't agree with this assessment -- the bug isn't really
about user error while operating on a narrow string, but about how the compiler
& library combo respond to that misuse. To wit, anytime a user gets a cryptic
error message buried deep inside a library in response to a simple mistake, you
have disempowered them from solving their own problem and derailed their
momentum in learning the language.
That said, under 2.058 the error message is now:
test.d(11): Error: cannot implicitly convert expression (start) of type
char[] to ulong
Which makes it clear that find(string, string) is returning a slice. I think
this specific issue should be closed.
--
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
More information about the Digitalmars-d-bugs
mailing list