Alfonso Garcia-Caro

My feedback

  1. 131 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  11 comments  ·  F# Language  ·  Flag idea as inappropriate…  ·  Admin →
    Alfonso Garcia-Caro commented  · 

    Having this will be tremendously beneficial when parsing TypeScript files to be used by Fable. Currently an extra type must be created to translate module functions in TypeScript with optional or ParamArray arguments.

    Alfonso Garcia-Caro supported this idea  · 
  2. 377 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  F# Language  ·  Flag idea as inappropriate…  ·  Admin →

    Strictly speaking this issue is not meant for https://fslang.uservoice.com, since it is about targeting a particular platform with the tooling, rather than the F# language or core library design itself.

    However, I’m leaving it open for now since it’s getting so many votes. We may close it sometime soon to release the votes.

    In any case, this work is planned by the Microsoft visualfsharp team and other contributors. Please contribute to the work at the http://github.com/Microsoft/visualfsharp repository and follow that repository for more details and updates.

    Relevant issues: https://github.com/Microsoft/visualfsharp/issues/387 and https://github.com/Microsoft/visualfsharp/pull/499

    Don Syme, F# Language and Core Library Evolution

    Alfonso Garcia-Caro supported this idea  · 
  3. 116 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  6 comments  ·  F# Language  ·  Flag idea as inappropriate…  ·  Admin →
  4. 39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  F# Language  ·  Flag idea as inappropriate…  ·  Admin →
    Alfonso Garcia-Caro supported this idea  · 
  5. 59 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  F# Language  ·  Flag idea as inappropriate…  ·  Admin →
    Alfonso Garcia-Caro supported this idea  · 
    Alfonso Garcia-Caro commented  · 

    Having a compiler flag to desugar options on reference types as null would increase performance when writing F# to be compiled into other languages like JavaScript.

  6. 67 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  F# Language  ·  Flag idea as inappropriate…  ·  Admin →
    Alfonso Garcia-Caro supported this idea  · 
  7. 248 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  8 comments  ·  F# Language  ·  Flag idea as inappropriate…  ·  Admin →
    Alfonso Garcia-Caro supported this idea  · 
  8. 457 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  37 comments  ·  F# Language  ·  Flag idea as inappropriate…  ·  Admin →
    Alfonso Garcia-Caro supported this idea  · 
    Alfonso Garcia-Caro commented  · 

    I would back the idea of having (.Name) just as syntactic sugar (with Intellisense, please) for (fun x -> x.Name)

  9. 311 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    23 comments  ·  F# Language  ·  Flag idea as inappropriate…  ·  Admin →

    I am generally in favour of addressing this in F# 4.x+. I would want seq { .. } and async { … } tailcalls to also be addressed.

    A more detailed design is needed and some trialling would be great. Jack’s work is a great start. However, this is not an easy piece of work to do in a non-invasive way and my own experiments in this area have not yet led to something I feel confident to include in the F# language design.

    An implementation and testing would need to be provided by someone in the F# community (possibly including Microsoft or Microsoft Research, though not limited to them).

    Currently, initial implementations of approved language design can be submitted as pull requests to the appropriate branch of https://github.com/Microsoft/visualfsharp. See http://fsharp.github.io/2014/06/18/fsharp-contributions.html for info on how to contribute to the F# language/core library design

    I encourage you to consider continue…

    Alfonso Garcia-Caro commented  · 

    I would be in favour of using the keyword, the attribute looks much more verbose...

Feedback and Knowledge Base