On Friday, 30 August 2013 at 13:32:31 UTC, Dmitry Olshansky wrote:
Now I'm in the same boat in the midst of wrok of applying new std.uni facilities to std.regex. As soon as std.array.array started using trusted lambda internally it doesn't accept any range with destructor.
Is the bug specific to trusted lambdas? I mean, would simply using a named function work around the problem?
If so, then we should simply patch array immediately, while waiting for a lambda improvement. Having a broken "std.array.array" is problematic for everyone...
