> > Sidenote: One convention from JS that I like is to name such event > > listeners as "on_<event_name>", e.g. "on_output_buffered". > > Thanks for bringing this up. I agree that "Upon X happening, do > this" is a very good convention to follow. I think the callback is > made whenever the child emits to the standard error stream, so > "on_error_output" (if we are worried that "error" has a too strong > "something bad happend" connotation, then perhaps "on_stderr_output" > may dampen it) perhaps? "on_stderr_output" sounds much better than "duplicate_output". I did spend much time trying to come up with a better name, but couldn't find anything that conveyed what the expected use case of this function was. Thanks, I'll rename it on my next reroll.
