Tim Keating <> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #2 from Tim Keating <> 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:
------- You are receiving this mail because: -------

Reply via email to