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

Investigate stack requirements for our alloc pattern #46

Open
mullr opened this issue Jul 17, 2019 · 0 comments
Open

Investigate stack requirements for our alloc pattern #46

mullr opened this issue Jul 17, 2019 · 0 comments

Comments

@mullr
Copy link
Collaborator

mullr commented Jul 17, 2019

There's some anecdotal evidence that our type-safe allocator pattern chews up a lot of stack. I believe that the optimizer mitigates this. Do some experiments to find out what's really going on.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mullr