You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am interested in learning from solutions to Raku/Perl weekly challenge that are readable and efficient - the second point I can not judge easily by just running the provided minimal testcases.
I was wondering if there is interest out there in automatically comparing different solutions in terms of scalability - meaning, what problem size can be solved in a fixed runtime.
First thoughts and a first shot #8644 and a github-action how an automated process might look like (look into "Run Benchmark" and scroll down a bit).
I put in the github-action also a small Tokei analysis, looking like below. Maybe this is usefull for some of us to find interesting solutions of other people.
No, closed on purpose. I could not solve the issue with the folder names - merging would only make sense if folders would not need to be renamed.Furthermore no one was interested in benchmarking the different solutions, not whithin a single language nor between languages.For me it is fine to leave it like it is. I am extracting interesting solutions using Tokei, then benchmark myself.Thank you for running the weekly challenge!Am 31.10.2023 um 17:20 schrieb Mohammad Sajid Anwar ***@***.***>:
Did you close the issue by mistake?
I thought this was supposed to be merged after few runs?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>
I am interested in learning from solutions to Raku/Perl weekly challenge that are readable and efficient - the second point I can not judge easily by just running the provided minimal testcases.
I was wondering if there is interest out there in automatically comparing different solutions in terms of scalability - meaning, what problem size can be solved in a fixed runtime.
First thoughts and a first shot #8644 and a github-action how an automated process might look like (look into "Run Benchmark" and scroll down a bit).
It looks like this:
After checkout try this:
I put in the github-action also a small Tokei analysis, looking like below. Maybe this is usefull for some of us to find interesting solutions of other people.
The text was updated successfully, but these errors were encountered: