"I didn't need this; why did they bother?"
As I mentioned, I'm not fussed by it but I was curious why they went to the effort when they have enough on their plate to do without taking this feature. I had not seen any demand for it in the forums (although I may have missed it) and thought that they would be busy with other, more in demand, features. I'm not saying that because I don't use it, no-one else should have it.
How does what do what?
Print without blocking.
Serial output isn't happening "in the background".
I'm still not clear on how it works.... If its not blocking execution of the code after the print statement and carries on execution of the subsequent code while still completing the print statement at a later time then that would seem like a background task. Just like on single processor PCs, where multitasking is not really concurrent multitasking but just faking it with time slicing very quickly.
It could still be incomplete two weeks later.
Does this mean that we should always use a flush after a print statment?
Cross post. Lefty answered most of this while I was writing.