Task Either IO

[FredericLatour]

Hi,
Maybe a stupid question, but why isn't there any TaskIO, TaskIOEither (or IOTask, IOTaskEither) ?
Could just be an alias that would make it possible to clarify from the signature that there is some side effect.
Does it make any sense at all ?

[steida]

IO is sync, Task is async

[samhh]

Task represents an asynchronous side effect, IO represents a synchronous side effect. The former essentially subsumes the latter so it would be nearly as redundant as OptionOption would be.

If you ever feel compelled to nest an IO inside a Task, instead lift the IO to a Task and monadic bind them together using something like Task.chainIOK.

[FredericLatour]

So the reasoning is that an asynchronous computation has necessarily side effects ?
Just trying to understand.

[samhh]

I can't think of anything pure that should be async. Lazy perhaps if it's expensive, but still sync.

[steida]

Time means something has an effect that takes time. Time itself is a side effect because it depends on something outside of your code.

[FredericLatour]

Makes sense (even though one can make any function async with just a keyword, I can't see indeed what would be the point).
So, as far as fp-ts is concerned, Task => side effect.
Thanks for clarifying.