Skip to content

Support multiple constraints on flexible types by #ILogger1 & #ILogger2 #1262

@Lanayx

Description

@Lanayx

Updated (@dsyme):

It seems reasonable to support a limited form of intersection type, e.g.

let f (env: #ILogger1 & #ILogger2) = ...

or also naming the type variable:

let f (env: 'T & #ILogger1 & #ILogger2) = ...

Since the F# 7 release there is a discrepancy between generic and non-generic restrictions, ie

allowed: env: 'T when ILogger<'T>
not allowed env: 'T when ILogger

Describe the solution you'd like

I propose to add support for non-generic case as well.

Describe alternatives you've considered

We can live with the old syntax env: 'T when 'T:> ILogger
Another possible syntax (covering multiple cases) could be env: #ILogger1 and #ILogger2

Pros and Cons

The advantages of making this adjustment to F#: this will allow to be more concise when dealing with a long list of restrictions, for example when implementing dependency injection based on the article https://bartoszsypytkowski.com/dealing-with-complex-dependency-injection-in-f/

The disadvantages of making this adjustment to F# are: one can say that this encourage type-level programming, but since this is the best (and probably the only) way to do scalable DI in F#, it's not an issue for me

Extra information

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

Related suggestions: (put links to related suggestions here)
dotnet/fsharp#14477

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

For Readers

If you would like to see this issue implemented, please click the 👍 emoji on this issue. These counts are used to generally order the suggestions by engagement.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions