“I don’t know why, but Combine split throwing/not throwing operators.”

You answered the question later on, performance.

Apple is using it internally in some high-performance libraries, and why setup do/try/catch blocks for each operator if the code doesn’t require it? I’m not sure I’ve ever relied on a map’s catch handler to turn a throwable error into a stream error.

Regardless, they’re there if you need ‘em.

Thanks for the link to my article, BTW.