This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of New status.
2848. Pass-through threshold for pool allocatorSection: 20.5.5.2 [mem.res.pool.options] Status: New Submitter: Jens Maurer Opened: 2016-12-15 Last modified: 2017-02-02
Priority: 3
View all issues with New status.
Discussion:
20.5.5.2 [mem.res.pool.options] p3 talks about a "pass-through-threshold".
First, the phrase is not defined and it seems it could be easily avoided given the context. Second, given the phrasing here, it seems the implementation is essentially allowed to ignore the valuelargest_required_pool_block as it sees fit. It is unclear whether that is the intention.
[2017-01-27 Telecon]
Priority 3; Jonathan will ask Alisdair for wording.
Proposed resolution:
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4