Skip to content
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

Sequence operation performance requirements for universal collection types #630

Open
johnwikman opened this issue Sep 12, 2022 · 0 comments

Comments

@johnwikman
Copy link
Contributor

In PR #628, there was an identified need to rework the seqCmp to increase the performance for lists. However, as this change would make things slower for ropes, it was decided to not integrate this change into the standard library. Instead Daniel will use this optimization locally instead.

For the future, it would be good to have a system with the universal collection types such that the most "optimal" sequence operation (such as comparison) would be chosen depending on the underlying opaque data structure. I could see this being solved by either expanding the number of intrinsic (or built-in) operations for universal collection types or have a hint-based system. I suppose the latter would relate to previous discussions about making all intrinsic operations as external definitions, with sufficient higher-level hints to allow the compiler to perform the necessary optimizations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant