aspiringuser

The heap allocation for the implementation won't be removed by LTO.

PIMPL pattern is great for reducing compilation time and creating stable user-facing APIs but it has a runtime cost. The "implementation" part is usually heap allocated and calling its methods have extra overhead of crossing the pointer to implementation barrier.

20 year C++ programmer here. I work on multithreaded server code. Stopped using modern C++ features 5 years ago. I'd compare my use of C++ to be roughly equivalent to the use of C++ in the NodeJS project or the V8 project. I'm not a user of Boost.

I have to agree with the author of the article. It takes longer to train developers to write idiosyncratic modern C++ code and compilation times explodes. Compiler support for bleeding edge C++ features is spotty at best. Harder to reason about the correctness of modern C++ code.

`cat | buble` did the trick! Thanks.

I continue to use babel 5.x which is much easier to use than babel 6.x which cannot be globally installed. Babel 5.x supports jsx by default. Would be great if buble would have feature parity with babel 5.x to ease the switch over.

Surely the AST is still produced? Acorn is the parser I assume?

rich_harris Yet another great project. Thanks.

Question - how to have buble accept input from stdin and output to stdout? This is useful for quick ES6 tests and chaining piped output.

buble with no args prints help. Would be more useful if it just started parsing code from stdin as babel 5.x did.