fixed [over.match.list]-related problem with eager value_type - #340
Merged
igaztanaga merged 1 commit intoAug 8, 2026
Merged
Conversation
Member
|
Many thanks Joaquin! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The following
fails in VS (and other compilers):
This is due to a sequence of happenstances:
boost::container::hubdefault ctor delegates tohub{allocator_type()}(note the braces).boost::anycan be constructed fromallocator_type(and from anything), make the compiler considerstd::initializer_listconstruction.std::initializer_listconstruction delegates tohub{il.begin(), il.end(), al_}.hub{il.begin(), il.end(), al_}is again formally valid as constructing from astd::initializer_listofboost::anys, and recursion ensues.The simple fix is replacing
{...}-style construction with(...)everywhere (not only for the default constructor).