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

About generational global roots in the manual #4743

Closed
vicuna opened this issue Mar 11, 2009 · 1 comment
Closed

About generational global roots in the manual #4743

vicuna opened this issue Mar 11, 2009 · 1 comment

Comments

@vicuna
Copy link

vicuna commented Mar 11, 2009

Original bug ID: 4743
Reporter: @alainfrisch
Status: closed (set by @xavierleroy on 2015-12-11T18:21:23Z)
Resolution: fixed
Priority: normal
Severity: minor
Target version: 4.01.0+dev
Fixed in version: 4.01.0+dev
Category: documentation
Monitored by: @hcarty

Bug description

  1. Chapter 18 mentions the new functions caml_register_generational_global_root and caml_remove_generational_global_root, but not caml_modify_generational_global_root. Moreover, the sentence "The garbage collector takes advantage of the guarantee that v is not modified to scan it less often." leads to believe that generational global roots are really immutable.

  2. My understanding is that the new interface is always more efficient for immutable value. However, assignment (through caml_modify_generational_global_root) can make the new interface slower than the old one, although the slowdown would usually be negligible. Is this correct? In which cases should we keep using the old interface instead of the new one?

@vicuna
Copy link
Author

vicuna commented Aug 2, 2013

Comment author: @damiendoligez

Changed the wording of the doc. (rev 13965)

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

No branches or pull requests

1 participant