Abel Braaksma
Abel Braaksma
Your example originally hot-started the tasks before the let-bang. After doing that, they cannot be parallelized anymore, depending how they were started (they may have started a child task, though,...
> The use case is very common - to collect data from several sources before doing some business logic with the combined object, Yes, it is indeed a common use...
Tx, but actually, reading "parallel" was the first time I understood what you were after (or maybe I still misunderstand, not sure now). Your example doesn't show a use-case (it's...
Much better! ❤️
yeah, that'll work a little bit. But keep in mind that F# tasks are hot. That means that `task2` (or `task1`) may already have finished before calling `Task.WhenAll` and they...
> That's the reason why it's so natural to do this for tasks and not for asyncs. Maybe I am missing something here, or just totally misunderstood your suggestion. Once...
Thanks. It does make your intent clearer. Imo, this should be governed by a user extension, as this is rather scary to open up. Besides, there are other suggestions with...
I think it makes sense to allow this, if indeed feasible. I wonder if it would also solve issues like #1360 (possibly using inline).
My current way of dealing with this is to split the union in nested unions, which improves performance for large DUs, but it's sub optimal at best. I'd be interested...
@happypig375, I think we should separate the proposals on using one field for same type DU's, and overlapping value types with explicit layout. There are many pitfalls for the latter,...