Peter Dimov

Then I suppose the default should be `false`. I don't remember why it isn't.

I feel like I'm not quite understanding the repercussions of this change. Is it true that (today) when we encode a URL, wherever `+` is allowed, it will stay `+`,...

> The problem is that we're not deciding between (a) `%20` instead of `+` by default for arbitrary strings I'm afraid I'm still missing something. `space_to_plus` is `false`: https://github.com/boostorg/url/blob/5ff23a35045fe948cfad8f305aef63a8b785bcac/include/boost/url/encode_opts.hpp#L35 So...

??

Judging by ``` INFO: tracking source dependencies of library container due to presence of "BOOST_CONTAINER_DECL memory_resource* new_delete_resource() BOOST_NOEXCEPT;" in file "boost\container\pmr\global_resource.hpp" ``` `bcp` has some heuristic to figure out when...

> I've already explained the reason above: src.cpp doesn't actually contain any function definitions. That's not what the word "explained" means. > I guess, we could put a fake function...

Oh, `bcp` supports giving it a name of a source file. So `dist\bin\bcp libs/json/src/src.cpp tmp-json\` works, kind of. It doesn't copy the `Jamfile` but it's not clear whether people who...

`dist\bin\bcp libs/json/src libs/json/build tmp-json\` then.

`bcp` has logic to copy the necessary files, which I've updated in https://github.com/boostorg/bcp/pull/5 to include `tools/boost-install` and `libs/headers`, but I don't know why it doesn't activate here.

I made a prototype, https://gist.github.com/pdimov/bcdaa4fef606fdcd0f21195a79bf8648 Unfortunately it's slower. But still cooler. :-) ``` 1.json: 74181420 bytes boost::json::parse: 456 ms x: -5.00063e-30, y: 5.00037e+30, z: 0.500451: 115 ms parse_into: 702 ms...