Vladimir Shchur

@gusty thanks a lot for the examples, they make your comment much clearer, but are you only concerned about this single case where both branches fail with exception? I agree,...

This will greatly help custom DSL for views, for example Oxpecker.ViewEngine: ```fsharp input(type'="text") // compiles fine input(type'="abcd") // compilation error, since it will be literal union violation ```

> It would cause way more harm than it could help and this can be achieved with other methods, smart constructors, myriad code generation, or even type providers In my...

> ```fsharp > type A = B | C;; > > > nameof C;; > val it: string = "C" > ``` > > same as your literals as types...

I agree that this is a nonstarter until [anonymous union types](https://github.com/fsharp/fslang-suggestions/issues/538) are implemented first, so not being in a rush. And when implemented, the string literal type logic should be...

When can this be released?

In agreement with @KevinRansom - here is the practice I follow: In `Directory.Packages.props`: ```xml true true ``` In `Directory.Build.props`: ```xml true ```

@KevinRansom agree, but it makes a big sense for Central Package Management. The idea is to manage all packages centrally including FSharp.Core and avoid duplicating this lines in every project.

This enhancement is approved for PR. Also see [Maintaners and support](https://github.com/fsprojects/pulsar-client-dotnet?tab=readme-ov-file#maintaners-and-support)

> Perhaps you mean that i can submit the PR myself ? Yes, that's correct