Abel Braaksma

I never considered this before, but this approach appears to work quite well, albeit with a few caveats (/cc @dsyme): ```f# type TaskSeq = static member isEmpty source : Task...

> is that it hinders reasoning about the code, Yes, this is certainly a downside. But the same could be said for the overload with the tupled arguments, as used...

> This would mean bringing a CancellableTask into this library from IcedTasks, which may be a good thing. Hmm, yes. But then the top lib name of `TaskSeq` should be...

@dsyme, see linked issue by @bartelink, #128. It's now a good time as any to discuss the scope of `Task` extensions and landing it. It appears that other libraries also...

> As of today .net core has the very limited support for resource files - microsoft/msbuild#2221 At the bottom of that thread it says it's fixed for Core 3.0.

@dsyme that would certainly simplify an addition like this, and would also allow `task` to support tail calls. Awesome! We can do some early-adoption testing here through `TaskSeq`.

See https://github.com/fsharp/fslang-suggestions/issues/1006 instead.

> reflection is achieved with F# functions, what you can see in Dashboard UI can appear rather clunky and misleading. perhaps an idea is to cast them to `Func`, which...

@pakrym-stripe, thanks for this. I didn't consider this possibility, tbh, and yes, that will allow us to use the HttpClientFactory with the current Stripe.NET implementation. From your referenced code: ```c#...

@isaacabraham, @cartermp, I just tried to repro Isaac's findings (also VS2017 15.3.1.0 P1, nightly of yesterday) and for a record field it pops up with the "apply where" box and...