Andrey Semashev

I would like the conditions to be instantiated only on demand, as it happens with `mpl::eval_if`. That is, if `cond1` evaluates to `true`, `cond1_2` should not be instantiated. This is...

I managed to convert the linked snippet to [this](https://github.com/boostorg/iterator/blob/a89865752f8f220b509f9912109f24c0465913a3/include/boost/iterator/detail/facade_iterator_category.hpp#L69-L91), but it took me about half an hour to get to this, and the solution doesn't scale as you can't nest...

In this case, I want to avoid unnecessary instantiations for performance reasons rather than correctness. That's how MPL code works and I definitely don't want to regress compared to that....

I tried benchmarking 100 instantiations of `iterator_facade_default_category` implemented with MPL (the original version I posted in https://github.com/boostorg/mp11/issues/105#issuecomment-2622303543), my MP11 version [here](https://github.com/boostorg/iterator/blob/a89865752f8f220b509f9912109f24c0465913a3/include/boost/iterator/detail/facade_iterator_category.hpp#L69-L91) and your "straightforward" version in gcc 13.3 with `-ftime-report`...

What version of wondershaper are you all using? The latest version in this git repo, 1.4.1, is not using CBQ and works fine on Debian 12. If you're all using...

If you're using a Debian package then the package version gives you the version. Debian packages are [1.1a](https://packages.debian.org/bookworm/wondershaper), which is outdated.

Also, vcpkg issues should be reported to Microsoft.

Also, as a general comment, please convert this to a draft PR until you consider everything done and ready for review.

Merged with some amendments. Thank you for your work.

There are other warnings further ahead, if compiled with `TBB_STRICT=OFF`, see the build log: [ubuntu-noble.log](https://github.com/user-attachments/files/23421653/ubuntu-noble.log)