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

Decompiler Bug: precedence of constructor call and other tupled calls not strong enough #7

Closed
GoogleCodeExporter opened this issue Jun 21, 2015 · 4 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter
Copy link

commented Jun 21, 2015

Example 1:

> source <@ String([|'h';'i'|]).Length @>;;
val it : string = "(String([|'h'; 'i'|])).Length"

Example 2:

> source <@ "asdf".Substring(1,2).Length @>;;
val it : string = "("asdf".Substring(1, 2)).Length"

Original issue reported on code.google.com by stephen....@gmail.com on 17 Feb 2011 at 8:30

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 21, 2015

Blocked: can't reconcile precedence of tupled arg applications from only 
available reference (the precedence table: 
http://msdn.microsoft.com/en-us/library/dd233228.aspx): applications of tupled 
calls need to be parenthesized, yet dot member calls on tupled calls need not.

Original comment by stephen....@gmail.com on 18 Feb 2011 at 5:34

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 21, 2015

I think I remember reading somewhere, that the F# teams actually went out of 
their way to make tupled calls bind less strongly in the presence of a lambda 
application.

Original comment by stephen....@gmail.com on 18 Jul 2011 at 5:52

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 21, 2015

Previous comment is true, was able to refactor precedence to take into account 
special cases like this.

Original comment by stephen....@gmail.com on 7 Aug 2011 at 6:46

  • Changed state: Fixed
@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 21, 2015

Original comment by stephen....@gmail.com on 18 Aug 2011 at 9:53

  • Added labels: Milestone-Release2.1.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.