Pike 9.0 quirk with implicit lambda

[Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum]

Hi Chris.

> In Pike 8 (tested on 8.1.15), the implicit lambda correctly receives
> its __ARGS__, and will happily provide those as closure variables. In
> Pike 9 (tested with current master, 235eb5), the inner function
> somehow causes __ARGS__ to be 0 instead of an array.
>
> Any ideas as to what's going on here? Am I misusing implicit lambdas?

Thanks for the report and testcase.

Fixed in Pike master as of a few minutes ago.

        /grubba