New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.max should warn if it sees useless :by parameter ( .max(:by(*.value)) ) #5987
Comments
From @AlexDanielCode: Result: Code: Result: I think :by(…) is something people commonly try (somebody did this on camelia, and I remember doing this myself), so it would be great if it could warn the user. |
From @zoffixznetOn Thu, 05 Jan 2017 07:59:29 -0800, alex.jakimenko@gmail.com wrote:
So why do people try it, anyway? Why that specific named param? I rather not litter the code with heuristics to catch arbitrary named params. |
The RT System itself - Status changed from 'new' to 'open' |
From @zoffixznetOn Wed, 26 Apr 2017 06:31:06 -0700, cpan@zoffix.com wrote:
I see our docs call the arg `&by` for this routine. I clarified[^1][^2] in [^1] Raku/doc@2f8f417 |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#130517 (status was 'resolved')
Searchable as RT130517$
The text was updated successfully, but these errors were encountered: