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 current behavior of the channel has a small issue for dropping behavior.
Currently, the values in the buffer will only be dropped when its overwritten, thus if the values used are expensive allocations
it will be helped by the channel until its overwritten by another value.
Would be nice to implement a smart behavior to drop the value as soon as the last possible reader reads it.
Maybe this could be implemented by keeping track of how many readers are possible at each node (keep track of number of readers?)
The text was updated successfully, but these errors were encountered:
The current behavior of the channel has a small issue for dropping behavior.
Currently, the values in the buffer will only be dropped when its overwritten, thus if the values used are expensive allocations
it will be helped by the channel until its overwritten by another value.
Would be nice to implement a smart behavior to drop the value as soon as the last possible reader reads it.
Maybe this could be implemented by keeping track of how many readers are possible at each node (keep track of number of readers?)
The text was updated successfully, but these errors were encountered: