Andrey Semashev
Andrey Semashev
The intention was that `BOOST_USE_WINAPI_VERSION` would be a Boost-wide macro that affects all libraries using Windows API.
I think, `tag_invoke` should win in the example above because the user explicitly provided it for the purpose of hashing while the Boost.Describe description could be used for arbitrary purpose....
Omitting the function object for an end iterator seems like a useful optimization, but the problem is that the end iterator can be made a non-end iterator by decrementing, and...
If there are still changes expected here, please, convert it to a draft.
As I said in the original post, the point of having fine grained includes is to reduce compile times. Which is why I'm asking the dedicated headers and don't want...
> Does not `` and `` suit your needs? No, because I don't need neither `concurrent_queue` nor `blocked_range` types where I need exceptions or `split`. > Or instead of ``...
> `user_abort` implementation is about 5-6 lines in header files. Moving it in a separate header file will add about 25-30 lines of service code (license, includes, namespaces, ...). So,...
As far as I can see, fine grained headers were not added yet, not in the latest TBB release. So yes, this is still relevant.
No, I did not perform the test.