You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is very similar to the existing Supervisor which allows to start a fiber, and bind its lifecycle to some outer scope. Here, we want to allocate a Resource and bind its lifecycle to the outer scope.
allocateSupervised (or superviseAllocated ?) would work like allocated, except in case the release is not invoked for some reason, it will be cleaned up once the supervisor scope ends.
tl;dr start is to allocated what supervise is to (we need something here :)
The text was updated successfully, but these errors were encountered:
This is an idea @TimWSpence and I cooked up once on Discord, starting from typelevel/fs2#2300 (comment).
The idea is very similar to the existing
Supervisor
which allows tostart
a fiber, and bind its lifecycle to some outer scope. Here, we want toallocate
aResource
and bind its lifecycle to the outer scope.allocateSupervised
(orsuperviseAllocated
?) would work likeallocated
, except in case therelease
is not invoked for some reason, it will be cleaned up once the supervisor scope ends.tl;dr
start
is toallocated
whatsupervise
is to (we need something here :)The text was updated successfully, but these errors were encountered: