Hadrian Tang

@kerams To stay in line with F#'s top-to-bottom left-to-right type inference, we would probably still need a type annotation at the top.

Related to #1029

Also VB.NET ```vb Imports System Public Class C ' no warning because C is obsolete Public Shared Sub Main() A() End Sub Public Shared Sub A() End Sub End Class...

@WhiteBlackGoose One thing to note is that C# does not care about whether the obsoletion is a warning or an error. https://sharplab.io/#v2:EYLgxg9gTgpgtADwGwBYA+ABATARgLABQhA2gPLADOEANjAC4wC6hGAzAATbsDC7A3oXZD2g4QHox7AHYR2AdwCGUKQEspAc3bAYYBQFcKMHuxUV2ESjXoxRQ7FhEFhz9gF4AfOwCCACgCUANy2js5klrQMPgBEUQA07HRQejB+zE7CbJw4SJwo3v78AL6ExURlmVzcOPzBwRLySqoaWjr6hjzVptIQdObh1sH2IS5CHvmBtelCYVQRTIMcGNm540UlhBsEFQ7cDgJTjsEzVgxpzvUyDcpqmtq6BkYAsgpqJmYWswMHQ8HOY74TA5HcifSIxeKJZKpBZZHIYPIAtYEQpAA==

Also there is ```fs Microsoft (R) F# Interactive version 11.4.2.0 for F# 5.0 Copyright (c) Microsoft Corporation. All Rights Reserved. For help type #help;; > {|T=typeof|};; {|T=typeof|};; ----------------^ stdin(39,17): error...

We can use this to support static lambdas, if we decide to do it.

@replicaJunction >without breaking changes to existing code. Consider type inference. There will be ambiguous overloads.

What about ranges with steps?

Very much in favor of this. Currently using Fable.React is annoying because of duplicated case names across HTMLAttr, CSSProp, and SVGAttr.

@nimzi A more tremendous win would be https://github.com/fsharp/fslang-suggestions/issues/538. I have always thought that nominal DUs are less suitable for describing "or" types in domain-driven design where structural unions are the...