search

JeffGarland / liaw2019-process

Repository for initial drafting of boost.process standards paper
MIT License
5 stars 4 forks source link

LEWGI Cologne: Do we need both basic_pipe and pipe streams? #34

Open JeffGarland opened 4 years ago

JeffGarland commented 4 years ago

Can we just have one or the other.

klemens-morgenstern commented 4 years ago

Basic pipe does the asio stuff, hence it's separate, because it needs an io_context. Pstream doesn't.

JeffGarland commented 4 years ago

Right -- I probably should have updated in that in the post-cologne draft we made pipe concrete. At the moment we've been able to hold the line on keeping async in and now the committee (concurrency study group SG1 and LEWG library evolution working group) have settled on a baseline for the executor design - http://wg21.link/P0433 - so we can now target that

klemens-morgenstern commented 4 years ago

I am by now of the opinion that the duplication is unneeded, i.e. just have the pstream interface implementing the iostream and the pipe following the networking TS patterns. Would simplify it a lot.