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

typer can wrongly eta-expand effectful expressions #7657

Closed
vicuna opened this issue Oct 11, 2017 · 4 comments
Closed

typer can wrongly eta-expand effectful expressions #7657

vicuna opened this issue Oct 11, 2017 · 4 comments
Assignees
Milestone

Comments

@vicuna
Copy link

vicuna commented Oct 11, 2017

Original bug ID: 7657
Reporter: @sliquister
Assigned to: @alainfrisch
Status: resolved (set by @xavierleroy on 2017-10-19T13:25:38Z)
Resolution: fixed
Priority: normal
Severity: major
Version: 4.05.0
Target version: 4.06.0 +dev/beta1/beta2/rc1
Category: typing
Monitored by: @gasche

Bug description

The following program should clearly raise:

let foo g () = g 1; ()
let f ?x y = ()

let _ = foo (assert false; f)

but it doesn't (with 4.05).

I think this is because the typer rewrites the argument of foo as:

let _ = foo (fun y -> (assert false; f) ?x:None y)

because it calls is_nonexpansive to decide if the expression is side-effect free, which doesn't work for sequences and other cases (the condition of if-then-else, patterns with lazy in them, etc).

(I didn't run into this in practice, I simply saw the call to
is_nonexpansive and thought that it couldn't be right)

@vicuna
Copy link
Author

vicuna commented Oct 11, 2017

Comment author: @alainfrisch

I wonder whether the compiler shouldn't be less clever and always let-bind the argument outside the eta-expanded function (as it does today when is_nonexpansive returns false). The common case where the argument is a simple identifier would be simplified by the Simplif pass anyway.

@vicuna
Copy link
Author

vicuna commented Oct 11, 2017

Comment author: @alainfrisch

is_nonexpansive also fails to detect reads from mutable locations, so

let foo g () = g 1; ()
let f1 ?x y = print_endline "f1"
let f2 ?x y = print_endline "f2"
let r = ref f1
let h = foo r.contents
let () = h (); r := f2; h ()

prints:

f1
f2

@vicuna
Copy link
Author

vicuna commented Oct 11, 2017

Comment author: @alainfrisch

#1424

@vicuna
Copy link
Author

vicuna commented Oct 19, 2017

Comment author: @xavierleroy

Pull request was merged in trunk and 4.06.

@vicuna vicuna closed this as completed Oct 19, 2017
@vicuna vicuna added the typing label Mar 14, 2019
@vicuna vicuna added this to the 4.06.0 milestone Mar 14, 2019
@vicuna vicuna added the bug label Mar 20, 2019
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

2 participants