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

struct tuple splatting #782

Happypig375 opened this issue Sep 15, 2019 · 0 comments


Copy link

commented Sep 15, 2019

struct tuple splatting

I propose we allow struct tuples to be inferred when applying to tuple functions.

static member M(x:struct(int * int) seq) = // struct tuples are C# friendly
    Seq.iter N x // FS0001 One tuple type is a struct tuple, the other is a reference tuple
static member N(x:int, y:int) =

The above code should be allowed.

The existing way of approaching this problem in F# is

static member M(x:struct(int * int) seq) =
    Seq.iter (fun struct (x, y) -> N(x, y)) x // Extra syntax
static member N(x:int, y:int) =
static member M(x:(int * int) seq) = // C# unfriendly reference tuples
    Seq.iter N x
static member N(x:int, y:int) =

Pros and Cons

The advantages of making this adjustment to F# are

  1. Parity between reference tuples and struct tuples
  2. Shorter and more concise code

The disadvantages of making this adjustment to F# are none that I can think of.

Extra information

Estimated cost (XS, S, M, L, XL, XXL): S

Related suggestions: No

Affidavit (please submit!)

Please tick this by placing a cross in the box:

  • This is not a question (e.g. like one you might ask on stackoverflow) and I have searched stackoverflow for discussions of this issue
  • I have searched both open and closed suggestions on this site and believe this is not a duplicate
  • This is not something which has obviously "already been decided" in previous versions of F#. If you're questioning a fundamental design decision that has obviously already been taken (e.g. "Make F# untyped") then please don't submit it.

Please tick all that apply:

  • This is not a breaking change to the F# language design
  • I or my company would be willing to help implement and/or test this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.