Heikki Vesterinen
Heikki Vesterinen
While I agree that changes to the default formatting should be carefully considered I would not like to see this kind of things added to the style guide. There are...
> > > > probably hundreds of rare formatting corner cases > > This totally isn't one, this involves [SynPat.LongIdent](https://fsharp.github.io/FSharp.Compiler.Service/reference/fsharp-compiler-syntaxtree-synpat.html) which has different offset rules in F# 5 than expressions....
When I encountered this some time ago I wasn't able to figure out a workaround without asking in Stackoverflow: https://stackoverflow.com/questions/66368514/how-to-call-extension-method-when-there-is-a-property-with-same-name
> There are some new options that the endpoint routing opens up though, I think the most realistic option would be to have an optional "descriptor" with each route. This...
> I believe that in case of Endpoint routing solution is using [Metadata API](https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.builder.endpointbuilder.metadata?view=aspnetcore-3.1#Microsoft_AspNetCore_Builder_EndpointBuilder_Metadata). So we would have, for example, `POST => withDocumentation => route "/sadas" (myHttpHandler)`. We could possibly...
After reading [this blog post](https://devblogs.microsoft.com/dotnet/configureawait-faq/) I'm wondering if it would be better to make the context insensitive builder the default, i.e. name it `task` and come up with some other...
> For me it's acceptable because backgroundTask fundamentally says "I want to get off this thread ASAP" - e.g. that the UI thread CPU resource is more important than any...
One further point in favor of using context insensitive task builder in library code. Testing or using library that uses context sensitive awaits in F# Interactive in Visual Studio is...