Oskar Gewalli

From what I can see it's already implemented in ocaml compatibility https://github.com/fsprojects/FSharp.Compatibility/blob/master/FSharp.Compatibility.OCaml/Pervasives.fs#L53-L59 ``` /// e1 == e2 tests for physical equality of e1 and e2. let inline ( == )...

How do you mean @dsyme ? I guess this property used often in c# isn't useful in regular f# code. I guess a workaround is to write an interface in...

Re @dsyme > Yes, if the collection property is settable this is true. The @= syntax does not feel intuitve however. Will think it over. Could you use the operators...

Why specifically `System.Text.Json` ?

I mean, the client shouldn't care about specific Json implementations? I don't know how many times I've had to inject some other Json library or configuration in order to get...

> I don't have the capacity for that. I sponsor part of this library development from my sallery. So if someone wants to present a solution I ready to discuss....

It looks as if it works as long as you use some of the same patterns as a .net core 2.1 webapp. Use the old format for program.cs.

Best bet is probably to migrate over [Lamar](https://github.com/JasperFx/lamar) instead since StructureMap is sunsetted @juanjoDiaz .

Interesting suggestion. Could we do it in such a way that users of the lib doesn't get confused? I'm thinking about having it in a module that you would have...

This looks a bit worrying. I've canceled the workflows, but it seems like I can reproduce the issue for F# core 5.0.2