Thread overview
[Issue 9184] std.algorithm.all fails to compile when providing a lambda
Feb 11, 2014
Peter Alexander
Feb 16, 2014
Peter Alexander
Feb 16, 2014
Peter Alexander
February 11, 2014
https://d.puremagic.com/issues/show_bug.cgi?id=9184


Peter Alexander <peter.alexander.au@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |peter.alexander.au@gmail.co
                   |                            |m
         Resolution|                            |WORKSFORME


--- Comment #2 from Peter Alexander <peter.alexander.au@gmail.com> 2014-02-11 11:48:08 PST ---
Was fixed in 2.063.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
February 14, 2014
https://d.puremagic.com/issues/show_bug.cgi?id=9184


jens.k.mueller@gmx.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WORKSFORME                  |FIXED


--- Comment #3 from jens.k.mueller@gmx.de 2014-02-14 00:20:44 PST ---
Thanks. Works here (Linux dmd v2.064) as well.
Don't know though which commit fixed it. It's *not* the one above.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
February 16, 2014
https://d.puremagic.com/issues/show_bug.cgi?id=9184


Peter Alexander <peter.alexander.au@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |WORKSFORME


--- Comment #4 from Peter Alexander <peter.alexander.au@gmail.com> 2014-02-16 14:29:26 PST ---
Changed to WORKSFORME so that it doesn't appear in the changelog for next update.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
February 16, 2014
https://d.puremagic.com/issues/show_bug.cgi?id=9184



--- Comment #5 from jens.k.mueller@gmx.de 2014-02-16 15:04:46 PST ---
Huh? Why WORKSFORME? Doesn't this imply that the issue cannot be reproduced? To me it's a bug and it got fixed.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
February 16, 2014
https://d.puremagic.com/issues/show_bug.cgi?id=9184



--- Comment #6 from Peter Alexander <peter.alexander.au@gmail.com> 2014-02-16 15:09:27 PST ---
(In reply to comment #5)
> Huh? Why WORKSFORME? Doesn't this imply that the issue cannot be reproduced? To me it's a bug and it got fixed.

But it was fixed in an earlier version, so it needs to be marked as WORKSFORME otherwise it will show up in the changelogs for the next version.

Mozilla even suggest this approach:

"In general you can resolve a bug as WFM if:
...
* the build the bug is reported against is more than one stable release old and
the bug can't be reproduced with a current build."

https://developer.mozilla.org/en/docs/What_to_do_and_what_not_to_do_in_Bugzilla#Resolving_bugs_as_WORKSFORME

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
February 16, 2014
https://d.puremagic.com/issues/show_bug.cgi?id=9184



--- Comment #7 from jens.k.mueller@gmx.de 2014-02-16 15:57:26 PST ---
I see. Only bugs that are closed in time are considered to be fixed (with
regard to the Changelog).

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