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: 5802 Reporter: turpin Assigned to:@garrigue Status: closed (set by @xavierleroy on 2015-12-11T18:21:08Z) Resolution: fixed Priority: low Severity: trivial Version: 4.00.1 Target version: 4.01.0+dev Fixed in version: 4.01.0+dev Category: typing
Bug description
In Typecore, "let" is used as a value name (to avoid changing side-effects when doing eta-expansion). For the purpose of unparsing typedtrees, "let" or "let" would be nicer.
The text was updated successfully, but these errors were encountered:
Maybe I'm wrong, but since the generated expression is 'let v = e in v', I believe that the variable name for v cannot interfere with anything, and can be chosen arbitrarily. Is that correct ?
Actually, the name is completely irrelevant, as it is not added to the environment (a fresh identifier is created in place).
I changed it to arg.
And due to the structure of the generated expression, there should be no shadowing introduced.
Precisely, what we get is something of the form:
let arg = in (fun eta -> arg ?lab1:None ... ?labn:None eta)
Original bug ID: 5802
Reporter: turpin
Assigned to: @garrigue
Status: closed (set by @xavierleroy on 2015-12-11T18:21:08Z)
Resolution: fixed
Priority: low
Severity: trivial
Version: 4.00.1
Target version: 4.01.0+dev
Fixed in version: 4.01.0+dev
Category: typing
Bug description
In Typecore, "let" is used as a value name (to avoid changing side-effects when doing eta-expansion). For the purpose of unparsing typedtrees, "let" or "let" would be nicer.
The text was updated successfully, but these errors were encountered: