The fact that `newSuspendedTransaction` closes the current transaction at the end of the block is cr...

# exposed

[Evan R.]

The fact that newSuspendedTransaction closes the current transaction at the end of the block is creating a real headache for me. I have suspend functions which will start a new suspended transaction on the IO dispatcher, but they cannot call other suspend functions doing the same thing. Is there a way around this that I’m not seeing? My current workaround is to make separate, private suspending functions which are exposed publicly via a newSuspendedTransaction block.

Untitled

[tapac]

Thank you for a report. I was able to reproduce and fix that behavior.
Will be available in the next release.

[Evan R.]

Thanks @tapac! The quick response and fix is much appreciated.

[maxmello]

I actually had the same problem and thought it was expected behavior, glad that this will work in the future