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
Table for complexity of common operations across backends #1726
Comments
|
If someone feels boring, here are all mentions of O(n) in clog. |
|
👍 on this. Anyway we have to decide where this table should be. Below language/operators or a new page like language/efficiency. The table itself can be filled by contributors later. |
|
It can also be on the FAQ page. Add a question like “What's the complexity of …?” and put a table there. |
That will be better :-) |
|
I've added a bunch of rows into the table. |
|
This would be quite complicated to maintain. And it's about implementation. |
|
I come back to this to ask for closing this issue. It does not belong to documentation (but to implementation) and it would be impossible ot maintain (checking the complexity of the operation whenever there's a change). So I'm asking for closing it, will do so in a couple of days if no one says anything for. |
See this: https://irclog.perlgeek.de/perl6/2017-11-16#i_15456401
And this: https://irclog.perlgeek.de/perl6/2017-12-31#i_15637372
This makes me want to have a table like this:
⚠ Feel free to edit this table!
Footnotes (use these for caveats and other notes):
ᵃ – …
ᵇ – …
ᶜ – …
The text was updated successfully, but these errors were encountered: