Skip to content

Auto-upcast values when type information is available #849

@Happypig375

Description

@Happypig375

I propose we auto-upcast values when type information is available.

The existing way of approaching this problem in F# is adding clucky upcast keywords.

let a : obj list = [1; 2; 3] // This works
let (^^) : seq<'a> -> seq<'a> -> seq<'a> = Seq.append
let a : int seq = [1; 2; 3] ^^ [4; 5; 6] // This also works
// But this doesn't?
let a : int seq = [1; 2; 3] // error FS0001: This expression was expected to have type 'seq<int>' but here has type ''a list'    

Pros and Cons

The advantages of making this adjustment to F# are

  1. Consistency with other scenarios where upcasting is implicit
  2. Conciseness
  3. Convenience

The disadvantage of making this adjustment to F# is the possibility of more inheritance-based code that are against F# philosophy.

Extra information

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

Related suggestions:
#3
#91
#536
#792

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions