Bug 9184 – std.algorithm.all fails to compile when providing a lambda

test.d --- unittest { import std.algorithm; assert(all!(a => a >= 0)([1, 2, 3])); } --- $ dmd -unittest -run test.d fails with Error: function test.__unittest3.not!(__lambda2).not!(int).not is a nested function and cannot be accessed from std.algorithm.find!(not,int[]).find Changing std.algorithm.all to return find!((a) => !unaryFun!pred(a))(range).empty; works. Though I'm not sure whether this is an appropriate fix. Please advice that I can create a pull request. $ dmd | head -1 DMD64 D Compiler v2.060

Commits pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/c834f350d11563f95246e79bae06a582e7fc2924 Fixes Issue 9184 - Document -op better. https://github.com/D-Programming-Language/dmd/commit/e849215dc9572da80b88c322aead62b01d70e11a Merge pull request #1860 from AndrejMitrovic/Fix9185_2 [trivial] Issue 9184 - Document -op better.

Was fixed in 2.063.

Thanks. Works here (Linux dmd v2.064) as well. Don't know though which commit fixed it. It's *not* the one above.

Changed to WORKSFORME so that it doesn't appear in the changelog for next update.

Huh? Why WORKSFORME? Doesn't this imply that the issue cannot be reproduced? To me it's a bug and it got fixed.

(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

I see. Only bugs that are closed in time are considered to be fixed (with regard to the Changelog).