kwiooim · HackerTrans

4 lata temudiscuss

Isn't this hard to make ergonomic in languages without higher-kinded types, because you need to specialize implementations of functions that otherwise could be generic over colors? like the filter() example in the original What Color is your Function post.

kwiooim

4 lata temudiscuss

Go solves the coloring issue without structured concurrency, that's true. But that statement says nothing about whether structured concurrency can or cannot solve the coloring issue, and if it could, then they're not orthogonal.

I think OP saying that structured concurrency solves the coloring problem is a very similar argument to the authors of Zig saying Zig is colorblind; it might be true for a portion of the userbase, mainly those who are callers, and mostly not for those who are library implementers.

I also think that the structured concurrency feature of "you can expect that the {thread, task, fiber, goroutine} is joned before the function returns" is weaker for the purpose of colorblindness than "you can expect that the {thread, task, fiber, goroutine} is joined before the next instruction is executed" which is what I think you'd need as a single tool for colorblindness

comments