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.

Sign up for GitHub

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

Jump to bottom

Use Non-Lexical Lifetimes to improve performance #41

Closed
andrew-johnson-4 opened this issue Aug 12, 2022 · 3 comments
Closed

Use Non-Lexical Lifetimes to improve performance #41

andrew-johnson-4 opened this issue Aug 12, 2022 · 3 comments
Labels
enhancement New feature or request performance Issues related to Code Optimization
Milestone
0.7

Comments

@andrew-johnson-4
Copy link
Owner

problem: there are entirely way too many clones in the type checker

solution: Non Lexical Lifetimes should enable smarter lifetimes.
@andrew-johnson-4 andrew-johnson-4 pinned this issue Nov 7, 2022
@andrew-johnson-4 andrew-johnson-4 added the performance Issues related to Code Optimization label Nov 23, 2022
@andrew-johnson-4
Copy link
Owner Author

This was being held up by some major confusion regarding .clone vs .cloned. A method for inspecting type signatures was added to a util module which should help clear up misunderstandings of what the actual type of something is.

@andrew-johnson-4 andrew-johnson-4 added this to the 0.7 milestone Dec 3, 2022
@andrew-johnson-4
Copy link
Owner Author

This ticket will be closed when cargo bench passes the 10k LOC example without optimizations turned on. Currently running that bench results in a stack overflow.

@andrew-johnson-4 andrew-johnson-4 added the enhancement New feature or request label Dec 7, 2022
@andrew-johnson-4
Copy link
Owner Author

LM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request performance Issues related to Code Optimization
Projects
None yet
Milestone
0.7
Development

No branches or pull requests
1 participant
@andrew-johnson-4