Dmitry

I think, you are correct, we don't have a way to set memory resource for the serializer at the moment.

I have a blueprint for the fix. I originally wanted to make the streambuffer to put all input into parser as soon as possible which would work OK with something...

The approach we described in the issue is somewhat different: 1. Serializer options are empty by default (not nulls). 2. If an option is empty and the corresponding special value...

Is this really true? We use init-lists in tests to create objects.

Ah, you mean that we should explicitly dissuade users from using complex init-list expressions?

After some investigation I discovered that this is due to optional header-only support (src.cpp does not contain any function definitions, `.ipp` files do). Unfortunately I don't think we can do...

I've already explained the reason above: src.cpp doesn't actually contain any function definitions. I guess, we could put a fake function into the file, but, IMO, that's silly. `bcp json...

Also, I suspect making bcp copy sources won't matter much, because building Json also depends on Config jam files, which aren't copied. At this point, it's simpler for users to...

There's essentially no point in copying src.cpp without copying build scripts.

I'm not at my computer, but IIRC, you also need at least boost-install and most of Config (not just the headers)