piaste

@rspeele Maybe see if the way [FSharp.Data.Npgsql](https://github.com/demetrixbio/FSharp.Data.Npgsql) does it could work for you? It's .NET Standard compatibile and it depends on Npgsql at compile time, but at a quick glance...

I've found an alternative approach that seems to work: instead of adding a `TypeMapper`, I can provide a custom `ReflectionService` that returns the type description for `T` with `IsNullable =...

@baleeds Sure, it's just a few lines of code: ``` type OptionReflectionService internal () = inherit DefaultReflectionService() override __.GetDescription (contextualType, defaultReferenceTypeNullHandling, settings) = if contextualType.OriginalType.IsGenericType && contextualType.OriginalType.GetGenericTypeDefinition() = typedefof then...

Yes, I hope to get the chance next week.

Do you have any project unloaded? If so, this is an old, unfixed issue: https://github.com/fsprojects/Paket.VisualStudio/issues/91#issuecomment-269271433

I know that @En3Tho mentioned it and I agree that they're a hack, but personally I use FSharp.UMX and I'm pretty happy. In addition to `open FSharp.UMX` I use the...

Considering the parameter name issue reported in #1145, does that not indicate that debug and release code should stay aligned? The OP says: > This is in theory a potential...

I will bring some anecdotal experience in favour of this proposal: 1) Before moving to F#, I used VB.NET for some years, which has had project-level imports since forever. We'd...

> I’m particularly aware that Fable and the Elmish design pattern is popularizing the use of immutable data for important model descriptions more and more and we should be helping...

:metal: I agree, type inference for collection literals sounds fantastic and, I suspect, a more efficient use of time than periodically introducing better data structures. Handling ambiguous cases should require...