You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose we allow overrides in modern SRTP syntax as the code below does not work
Only the last Slice: int -> 'c method override condition is resolved but no one before the last
openSystem.Runtime.CompilerServices[<Extension>]typeSliceExtensions=[<Extension>]static member inlineGetSlice<'cwhen'c:(member Slice:int *int ->'c)and'c:(member Slice:int ->'c)and'c:(member Length:int)>(source:'c,from:int option,``to``:int option)=match from,``to``with| Some from, Some ``to``-> source.Slice(from,``to``+1- from)| Some from, None -> source.Slice(from)| None, Some ``to``-> source.Slice(0,``to``+1)| None, None -> source.Slice(0,1)openSystem.Collections.Immutableletarr=seq{0;1;2;3;4}|> ImmutableArray.CreateRange
arr[..2]
If you swap
when 'c :(memberSlice: int * int -> 'c)and 'c :(member Slice:int -> 'c)
as
when 'c :(memberSlice: int -> 'c)and 'c :(member Slice:int *int -> 'c)
the compiler will use the the second one again but not both
The existing way of approaching this problem in F# is to use old SRTP syntax
Pros and Cons
The advantages of making this adjustment to F# are code amount reduction
The disadvantages of making this adjustment to F# are not exist
Extra information
Estimated cost (XS, S, M, L, XL, XXL): S
Related suggestions:
Affidavit (please submit!)
Please tick these items 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
This is a language change and not purely a tooling change (e.g. compiler bug, editor support, warning/error messages, new warning, non-breaking optimisation) belonging to the compiler and tooling repository
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
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.
The text was updated successfully, but these errors were encountered:
I propose we allow overrides in modern SRTP syntax as the code below does not work
Only the last
Slice: int -> 'c
method override condition is resolved but no one before the lastIf you swap
as
the compiler will use the the second one again but not both
The existing way of approaching this problem in F# is to use old SRTP syntax
Pros and Cons
The advantages of making this adjustment to F# are code amount reduction
The disadvantages of making this adjustment to F# are not exist
Extra information
Estimated cost (XS, S, M, L, XL, XXL): S
Related suggestions:
Affidavit (please submit!)
Please tick these items by placing a cross in the box:
Please tick all that apply:
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.
The text was updated successfully, but these errors were encountered: