You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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?
The text was updated successfully, but these errors were encountered:
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
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.
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?
The text was updated successfully, but these errors were encountered: