Hi Isaac, I have spent some time looking at this and I believe this would be a change vs the docstring and current behavior so I don’t think this is going to be applied as is. The open question is whether there should be some alternate version that does what you’re looking for. I think for now, you would be better off using your own custom function that does what you want (not sure why you need a whole version of core.async just for that).

These years, I must use my version of core.async, because of this bug

Hi Isaac, I have spent some time looking at this despite appearances here, but I’m not sure yet what we should do and whether this is the right way to do it. I maintain dozens of projects and so I only cycle through this one periodically to focus on things so it will likely be more weeks before I get back to it.

wow! Still no progress,