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

Implement a moving/compacting collector #41

Open
Others opened this issue Aug 1, 2020 · 0 comments
Open

Implement a moving/compacting collector #41

Others opened this issue Aug 1, 2020 · 0 comments
Labels
T-enhancement New feature or request T-optimization Something is slower than it needs to be

Comments

@Others
Copy link
Owner

Others commented Aug 1, 2020

Since we have the whole GcHandle system, we have a nice way of figuring out if something can be moved or not. Could we exploit this to create a compacting collector somehow?

We'd need to be careful, because the worst case is probably someone holding a GcHandle forever. (Meaning we'd need to keep that data live.)

Note:

  • This would prevent us allowing situational deref
  • The perf win is probably not too much since we need to allocate for every handle anyway
  • This should probably be done as part of a larger effort to make the backend pluggable
@Others Others added T-enhancement New feature or request T-optimization Something is slower than it needs to be labels Aug 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-enhancement New feature or request T-optimization Something is slower than it needs to be
Projects
None yet
Development

No branches or pull requests

1 participant