Gábor Csárdi

But then with `implements` we need to take care about inheriting interfaces, etc.

But then if we have new syntax, we might as well do the original suggestion in #9. Maybe.

Thanks! AFAICT that change was reverted, so everything should be fine soonish: https://github.com/wch/r-source/commit/ef0a4a211f92640e71e87cbe7b66323f2c239e4d We can keep this issue open, we might as well work around this at the next release.

The problem with that, is that we need to figure out what to do if the specified format does not match the progress data. E.g. if you have `"[:bar] :percent"`...

Yeah, exactly. I think we can have a global stack of active progress bars. In displays that only support one progress bar, most notably R Studio, we would only show...

@jimhester that is smart, but also very limited, unfortunately.

I am not using it myself, and if it is low priority for you, then I am worried about long term maintenance.

I don't mind adding it, hopefully we can find some users. Some concerns: * It might not be easy or even possible to use their cli client w/o a terminal....

This is now implemented in asciicast, and it works pretty well. It is not clear if we should port it to callr or processx, maybe the the former?

FWIW I don't think you need any workarounds if you define your methods "inline". E.g. here is a simple example: https://github.com/r-lib/progress/blob/master/R/progress.R#L179