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: 7356 Reporter:@yallop Status: acknowledged (set by @damiendoligez on 2016-09-28T11:50:22Z) Resolution: open Priority: normal Severity: feature Target version: 4.05.0 +dev/beta1/beta2/beta3/rc1 Category: documentation Monitored by: braibant @dbuenzli
Bug description
flambda's optimisations can change whether a value is finalisable. For example, the following program executes without error when compiled with 4.04.0+beta1, but exits with an exception (Invalid_argument("Gc.finalise")) when compiled with 4.04.0+beta1+flambda
letfx=Gc.finalise ignore (fun() -> x; ())
let()= f ()
A section on finalisability would fit well in the flambda chapter alongside the sections about inhibition of optimisation (20.14) and about unsafe operations (20.15).
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.
Original bug ID: 7356
Reporter: @yallop
Status: acknowledged (set by @damiendoligez on 2016-09-28T11:50:22Z)
Resolution: open
Priority: normal
Severity: feature
Target version: 4.05.0 +dev/beta1/beta2/beta3/rc1
Category: documentation
Monitored by: braibant @dbuenzli
Bug description
flambda's optimisations can change whether a value is finalisable. For example, the following program executes without error when compiled with 4.04.0+beta1, but exits with an exception (Invalid_argument("Gc.finalise")) when compiled with 4.04.0+beta1+flambda
A section on finalisability would fit well in the flambda chapter alongside the sections about inhibition of optimisation (20.14) and about unsafe operations (20.15).
The text was updated successfully, but these errors were encountered: