<!doctype html><html lang="en">
 <head>
  <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  <meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport">
  <title>P3020R0: 2023-09 Library Evolution Poll Outcomes</title>
<style data-fill-with="stylesheet">/******************************************************************************
 *                   Style sheet for the W3C specifications                   *
 *
 * Special classes handled by this style sheet include:
 *
 * Indices
 *   - .toc for the Table of Contents (<ol class="toc">)
 *     + <span class="secno"> for the section numbers
 *   - #toc for the Table of Contents (<nav id="toc">)
 *   - ul.index for Indices (<a href="#ref">term</a><span>, in § N.M</span>)
 *   - table.index for Index Tables (e.g. for properties or elements)
 *
 * Structural Markup
 *   - table.data for general data tables
 *     -> use 'scope' attribute, <colgroup>, <thead>, and <tbody> for best results !
 *     -> use <table class='complex data'> for extra-complex tables
 *     -> use <td class='long'> for paragraph-length cell content
 *     -> use <td class='pre'> when manual line breaks/indentation would help readability
 *   - dl.switch for switch statements
 *   - ol.algorithm for algorithms (helps to visualize nesting)
 *   - .figure and .caption (HTML4) and figure and figcaption (HTML5)
 *     -> .sidefigure for right-floated figures
 *   - ins/del
 *     -> ins/del.c### for candidate and proposed changes (amendments)
 *
 * Code
 *   - pre and code
 *
 * Special Sections
 *   - .note       for informative notes             (div, p, span, aside, details)
 *   - .example    for informative examples          (div, p, pre, span)
 *   - .issue      for issues                        (div, p, span)
 *   - .advisement for loud normative statements     (div, p, strong)
 *   - .annoying-warning for spec obsoletion notices (div, aside, details)
 *   - .correction for "candidate corrections"       (div, aside, details, section)
 *   - .addition   for "candidate additions"         (div, aside, details, section)
 *   - .correction.proposed for "proposed corrections" (div, aside, details, section)
 *   - .addition.proposed   for "proposed additions"   (div, aside, details, section)
 *
 * Definition Boxes
 *   - pre.def   for WebIDL definitions
 *   - table.def for tables that define other entities (e.g. CSS properties)
 *   - dl.def    for definition lists that define other entitles (e.g. HTML elements)
 *
 * Numbering
 *   - .secno for section numbers in .toc and headings (<span class='secno'>3.2</span>)
 *   - .marker for source-inserted example/figure/issue numbers (<span class='marker'>Issue 4</span>)
 *   - ::before styled for CSS-generated issue/example/figure numbers:
 *     -> Documents wishing to use this only need to add
 *        figcaption::before,
 *        .caption::before { content: "Figure "  counter(figure) " ";  }
 *        .example::before { content: "Example " counter(example) " "; }
 *        .issue::before   { content: "Issue "   counter(issue) " ";   }
 *
 * Header Stuff (ignore, just don't conflict with these classes)
 *   - .head for the header
 *   - .copyright for the copyright
 *
 * Outdated warning for old specs
 *
 * Miscellaneous
 *   - .overlarge for things that should be as wide as possible, even if
 *     that overflows the body text area. This can be used on an item or
 *     on its container, depending on the effect desired.
 *     Note that this styling basically doesn't help at all when printing,
 *     since A4 paper isn't much wider than the max-width here.
 *     It's better to design things to fit into a narrower measure if possible.
 *
 *   - js-added ToC jump links (see fixup.js)
 *
 ******************************************************************************/

/* color variables included separately for reliability */

/******************************************************************************/
/*                                    Body                                    */
/******************************************************************************/

	html {
	}

	body {
		counter-reset: example figure issue;

		/* Layout */
		max-width: 50em;			  /* limit line length to 50em for readability   */
		margin: 0 auto;				/* center text within page                    */
		padding: 1.6em 1.5em 2em 50px; /* assume 16px font size for downlevel clients */
		padding: 1.6em 1.5em 2em calc(26px + 1.5em); /* leave space for status flag    */

		/* Typography */
		line-height: 1.5;
		font-family: sans-serif;
		widows: 2;
		orphans: 2;
		word-wrap: break-word;
		overflow-wrap: break-word;
		hyphens: auto;

		color: black;
		color: var(--text);
		background: white top left fixed no-repeat;
		background: var(--bg) top left fixed no-repeat;
		background-size: 25px auto;
	}


/******************************************************************************/
/*                         Front Matter & Navigation                          */
/******************************************************************************/

/** Header ********************************************************************/

	div.head { margin-bottom: 1em; }
	div.head hr { border-style: solid; }

	div.head h1 {
		font-weight: bold;
		margin: 0 0 .1em;
		font-size: 220%;
	}

	div.head h2 { margin-bottom: 1.5em;}

/** W3C Logo ******************************************************************/

	.head .logo {
		float: right;
		margin: 0.4rem 0 0.2rem .4rem;
	}

	.head img[src*="logos/W3C"] {
		display: block;
		border: solid #1a5e9a;
		border: solid var(--logo-bg);
		border-width: .65rem .7rem .6rem;
		border-radius: .4rem;
		background: #1a5e9a;
		background: var(--logo-bg);
		color: white;
		color: var(--logo-text);
		font-weight: bold;
	}

	.head a:hover > img[src*="logos/W3C"],
	.head a:focus > img[src*="logos/W3C"] {
		opacity: .8;
	}

	.head a:active > img[src*="logos/W3C"] {
		background: #c00;
		background: var(--logo-active-bg);
		border-color: #c00;
		border-color: var(--logo-active-bg);
	}

	/* see also additional rules in Link Styling section */

/** Copyright *****************************************************************/

	p.copyright,
	p.copyright small { font-size: small; }

/** Back to Top / ToC Toggle **************************************************/

	@media print {
		#toc-nav {
			display: none;
		}
	}
	@media not print {
		#toc-nav {
			position: fixed;
			z-index: 3;
			bottom: 0; left: 0;
			margin: 0;
			min-width: 1.33em;
			border-top-right-radius: 2rem;
			box-shadow: 0 0 2px;
			font-size: 1.5em;
		}
		#toc-nav > a {
			display: block;
			white-space: nowrap;

			height: 1.33em;
			padding: .1em 0.3em;
			margin: 0;

			box-shadow: 0 0 2px;
			border: none;
			border-top-right-radius: 1.33em;

			color: #707070;
			color: var(--tocnav-normal-text);
			background: white;
			background: var(--tocnav-normal-bg);
		}
		#toc-nav > a:hover,
		#toc-nav > a:focus {
			color: black;
			color: var(--tocnav-hover-text);
			background: #f8f8f8;
			background: var(--tocnav-hover-bg);
		}
		#toc-nav > a:active {
			color: #c00;
			color: var(--tocnav-active-text);
			background: white;
			background: var(--tocnav-active-bg);
		}

		#toc-nav > #toc-jump {
			padding-bottom: 2em;
			margin-bottom: -1.9em;
		}

		/* statusbar gets in the way on keyboard focus; remove once browsers fix */
		#toc-nav > a[href="#toc"]:not(:hover):focus:last-child {
			padding-bottom: 1.5rem;
		}

		#toc-nav:not(:hover) > a:not(:focus) > span + span {
			/* Ideally this uses :focus-within on #toc-nav */
			display: none;
		}
		#toc-nav > a > span + span {
			padding-right: 0.2em;
		}
	}

/** ToC Sidebar ***************************************************************/

	/* Floating sidebar */
	@media screen {
		body.toc-sidebar #toc {
			position: fixed;
			top: 0; bottom: 0;
			left: 0;
			width: 23.5em;
			max-width: 80%;
			max-width: calc(100% - 2em - 26px);
			overflow: auto;
			padding: 0 1em;
			padding-left: 42px;
			padding-left: calc(1em + 26px);
			color: black;
			color: var(--tocsidebar-text);
			background: inherit;
			background-color: #f7f8f9;
			background-color: var(--tocsidebar-bg);
			z-index: 1;
			box-shadow: -.1em 0 .25em rgba(0,0,0,.1) inset;
			box-shadow: -.1em 0 .25em var(--tocsidebar-shadow) inset;
		}
		body.toc-sidebar #toc h2 {
			margin-top: .8rem;
			font-variant: small-caps;
			font-variant: all-small-caps;
			text-transform: lowercase;
			font-weight: bold;
			color: gray;
			color: hsla(203,20%,40%,.7);
			color: var(--tocsidebar-heading-text);
		}
		body.toc-sidebar #toc-jump:not(:focus) {
			width: 0;
			height: 0;
			padding: 0;
			position: absolute;
			overflow: hidden;
		}
	}
	/* Hide main scroller when only the ToC is visible anyway */
	@media screen and (max-width: 28em) {
		body.toc-sidebar {
			overflow: hidden;
		}
	}

	/* Sidebar with its own space */
	@media screen and (min-width: 78em) {
		body:not(.toc-inline) #toc {
			position: fixed;
			top: 0; bottom: 0;
			left: 0;
			width: 23.5em;
			overflow: auto;
			padding: 0 1em;
			padding-left: 42px;
			padding-left: calc(1em + 26px);
			color: black;
			color: var(--tocsidebar-text);
			background: inherit;
			background-color: #f7f8f9;
			background-color: var(--tocsidebar-bg);
			z-index: 1;
			box-shadow: -.1em 0 .25em rgba(0,0,0,.1) inset;
			box-shadow: -.1em 0 .25em var(--tocsidebar-shadow) inset;
		}
		body:not(.toc-inline) #toc h2 {
			margin-top: .8rem;
			font-variant: small-caps;
			font-variant: all-small-caps;
			text-transform: lowercase;
			font-weight: bold;
			color: gray;
			color: hsla(203,20%,40%,.7);
			color: var(--tocsidebar-heading-text);
		}

		body:not(.toc-inline) {
			padding-left: 29em;
		}
		/* See also Overflow section at the bottom */

		body:not(.toc-inline) #toc-jump:not(:focus) {
			width: 0;
			height: 0;
			padding: 0;
			position: absolute;
			overflow: hidden;
		}
	}
	@media screen and (min-width: 90em) {
		body:not(.toc-inline) {
			margin: 0 4em;
		}
	}

/******************************************************************************/
/*                                Sectioning                                  */
/******************************************************************************/

/** Headings ******************************************************************/

	h1, h2, h3, h4, h5, h6, dt {
		page-break-after: avoid;
		page-break-inside: avoid;
		font: 100% sans-serif;   /* Reset all font styling to clear out UA styles */
		font-family: inherit;	/* Inherit the font family. */
		line-height: 1.2;		/* Keep wrapped headings compact */
		hyphens: manual;		/* Hyphenated headings look weird */
	}

	h2, h3, h4, h5, h6 {
		margin-top: 3rem;
	}

	h1, h2, h3 {
		color: #005A9C;
		color: var(--heading-text);
	}

	h1 { font-size: 170%; }
	h2 { font-size: 140%; }
	h3 { font-size: 120%; }
	h4 { font-weight: bold; }
	h5 { font-style: italic; }
	h6 { font-variant: small-caps; }
	dt { font-weight: bold; }

/** Subheadings ***************************************************************/

	h1 + h2,
	#profile-and-date {
		/* #profile-and-date is a subtitle in an H2 under the H1 */
		margin-top: 0;
	}
	h2 + h3,
	h3 + h4,
	h4 + h5,
	h5 + h6 {
		margin-top: 1.2em; /* = 1 x line-height */
	}

/** Section divider ***********************************************************/

	:not(.head) > :not(.head) + hr {
		font-size: 1.5em;
		text-align: center;
		margin: 1em auto;
		height: auto;
		color: black;
		color: var(--hr-text);
		border: transparent solid 0;
		background: transparent;
	}
	:not(.head) > hr::before {
		content: "\2727\2003\2003\2727\2003\2003\2727";
	}

/******************************************************************************/
/*                            Paragraphs and Lists                            */
/******************************************************************************/

	p {
		margin: 1em 0;
	}

	dd > p:first-child,
	li > p:first-child {
		margin-top: 0;
	}

	ul, ol {
		margin-left: 0;
		padding-left: 2em;
	}

	li {
		margin: 0.25em 0 0.5em;
		padding: 0;
	}

	dl dd {
		margin: 0 0 .5em 2em;
	}

	.head dd + dd { /* compact for header */
		margin-top: -.5em;
	}

	/* Style for algorithms */
	ol.algorithm ol:not(.algorithm),
	.algorithm > ol ol:not(.algorithm) {
	border-left: 0.5em solid #DEF;
	border-left: 0.5em solid var(--algo-border);
	}

	/* Put nice boxes around each algorithm. */
	[data-algorithm]:not(.heading) {
	 padding: .5em;
	 border: thin solid #ddd;
	 border: thin solid var(--algo-border);
	 border-radius: .5em;
	 margin: .5em calc(-0.5em - 1px);
	}
	[data-algorithm]:not(.heading) > :first-child {
	 margin-top: 0;
	}
	[data-algorithm]:not(.heading) > :last-child {
	 margin-bottom: 0;
	}

	/* Style for switch/case <dl>s */
	dl.switch > dd > ol.only,
	dl.switch > dd > .only > ol {
	margin-left: 0;
	}
	dl.switch > dd > ol.algorithm,
	dl.switch > dd > .algorithm > ol {
	margin-left: -2em;
	}
	dl.switch {
	padding-left: 2em;
	}
	dl.switch > dt {
	text-indent: -1.5em;
	margin-top: 1em;
	}
	dl.switch > dt + dt {
	margin-top: 0;
	}
	dl.switch > dt::before {
	content: '\21AA';
	padding: 0 0.5em 0 0;
	display: inline-block;
	width: 1em;
	text-align: right;
	line-height: 0.5em;
	}

/** Terminology Markup ********************************************************/


/******************************************************************************/
/*                                 Inline Markup                              */
/******************************************************************************/

/** Terminology Markup ********************************************************/
	dfn   { /* Defining instance */
		font-weight: bolder;
	}
	a > i { /* Instance of term */
		font-style: normal;
	}
	dt dfn code, code.idl {
		font-size: inherit;
	}
	dfn var {
		font-style: normal;
	}

/** Change Marking ************************************************************/

	del {
		color: #aa0000;
		color: var(--del-text);
		background: transparent;
		background: var(--del-bg);
		text-decoration: line-through;
	}
	ins {
		color: #006100;
		color: var(--ins-text);
		background: transparent;
		background: var(--ins-bg);
		text-decoration: underline;
	}

	/* for amendments (candidate/proposed changes) */

	.amendment ins, .correction ins, .addition ins,
	ins[class^=c] {
		text-decoration-style: dotted;
	}
	.amendment del, .correction del, .addition del,
	del[class^=c] {
		text-decoration-style: dotted;
	}
	.amendment.proposed ins, .correction.proposed ins, .addition.proposed ins,
	ins[class^=c].proposed {
		text-decoration-style: double;
	}
	.amendment.proposed del, .correction.proposed del, .addition.proposed del,
	del[class^=c].proposed {
		text-decoration-style: double;
	}

/** Miscellaneous improvements to inline formatting ***************************/

	sup {
		vertical-align: super;
		font-size: 80%
	}

/******************************************************************************/
/*                                    Code                                    */
/******************************************************************************/

/** General monospace/pre rules ***********************************************/

	pre, code, samp {
		font-family: Menlo, Consolas, "DejaVu Sans Mono", Monaco, monospace;
		font-size: .9em;
		hyphens: none;
		text-transform: none;
		text-align: left;
		text-align: start;
		font-variant: normal;
		orphans: 3;
		widows: 3;
		page-break-before: avoid;
	}
	pre code,
	code code {
		font-size: 100%;
	}

	pre {
		margin-top: 1em;
		margin-bottom: 1em;
		overflow: auto;
	}

/** Inline Code fragments *****************************************************/

	/* Do something nice. */

/******************************************************************************/
/*                                    Links                                   */
/******************************************************************************/

/** General Hyperlinks ********************************************************/

	/* We hyperlink a lot, so make it less intrusive */
	a[href] {
		color: #034575;
		color: var(--a-normal-text);
		text-decoration: underline #707070;
		text-decoration: underline var(--a-normal-underline);
		text-decoration-skip-ink: none;
	}
	a:visited {
		color: #034575;
		color: var(--a-visited-text);
		text-decoration-color: #bbb;
		text-decoration-color: var(--a-visited-underline);
	}

	/* Indicate interaction with the link */
	a[href]:focus,
	a[href]:hover {
		text-decoration-thickness: 2px;
	}
	a[href]:active {
		color: #c00;
		color: var(--a-active-text);
		text-decoration-color: #c00;
		text-decoration-color: var(--a-active-underline);
	}

	/* Backout above styling for W3C logo */
	.head .logo,
	.head .logo a {
		border: none;
		text-decoration: none;
		background: transparent;
	}

/******************************************************************************/
/*                                    Images                                  */
/******************************************************************************/

	img {
		border-style: none;
	}

	img, svg {
		/* Intentionally not color-scheme aware. */
		background: white;
	}

	/* For autogen numbers, add
	  .caption::before, figcaption::before { content: "Figure " counter(figure) ". "; }
	*/

	figure, .figure, .sidefigure {
		page-break-inside: avoid;
		text-align: center;
		margin: 2.5em 0;
	}
	.figure img,	.sidefigure img,	figure img,
	.figure object, .sidefigure object, figure object {
		max-width: 100%;
		margin: auto;
		height: auto;
	}
	.figure pre, .sidefigure pre, figure pre {
		text-align: left;
		display: table;
		margin: 1em auto;
	}
	.figure table, figure table {
		margin: auto;
	}
	@media screen and (min-width: 20em) {
		.sidefigure {
			float: right;
			width: 50%;
			margin: 0 0 0.5em 0.5em;
		}
	}
	.caption, figcaption, caption {
		font-style: italic;
		font-size: 90%;
	}
	.caption::before, figcaption::before, figcaption > .marker {
		font-weight: bold;
	}
	.caption, figcaption {
		counter-increment: figure;
	}

	/* DL list is indented 2em, but figure inside it is not */
	dd > .figure, dd > figure { margin-left: -2em; }

/******************************************************************************/
/*                             Colored Boxes                                  */
/******************************************************************************/

	.issue, .note, .example, .assertion, .advisement, blockquote,
	.amendment, .correction, .addition {
		margin: 1em auto;
		padding: .5em;
		border: .5em;
		border-left-style: solid;
		page-break-inside: avoid;
	}
	span.issue, span.note {
		padding: .1em .5em .15em;
		border-right-style: solid;
	}

	blockquote > :first-child,
	.note  > p:first-child,
	.issue > p:first-child,
	.amendment > p:first-child,
	.correction > p:first-child,
	.addition > p:first-child {
		margin-top: 0;
	}
	blockquote > :last-child,
	.note  > p:last-child,
	.issue > p:last-child,
	.amendment > p:last-child,
	.correction > p:last-child,
	.addition > p:last-child {
		margin-bottom: 0;
	}


	.issue::before, .issue > .marker,
	.example::before, .example > .marker,
	.note::before, .note > .marker,
	details.note > summary > .marker,
	.amendment::before, .amendment > .marker,
	details.amendment > summary > .marker,
	.addition::before, .addition > .marker,
	addition.amendment > summary > .marker,
	.correction::before, .correction > .marker,
	correction.amendment > summary > .marker
	{
		text-transform: uppercase;
		padding-right: 1em;
	}

	.example::before, .example > .marker {
		display: block;
		padding-right: 0em;
	}

/** Blockquotes ***************************************************************/

	blockquote {
		border-color: silver;
		border-color: var(--blockquote-border);
		background: transparent;
		background: var(--blockquote-bg);
		color: currentcolor;
		color: var(--blockquote-text);
	}

/** Open issue ****************************************************************/

	.issue {
		border-color: #e05252;
		border-color: var(--issue-border);
		background: #fbe9e9;
		background: var(--issue-bg);
		color: black;
		color: var(--issue-text);
		counter-increment: issue;
		overflow: auto;
	}
	.issue::before, .issue > .marker {
		color: #831616;
		color: var(--issueheading-text);
	}
	/* Add .issue::before { content: "Issue " counter(issue) " "; } for autogen numbers,
	  or use class="marker" to mark up the issue number in source. */

/** Example *******************************************************************/

	.example {
		border-color: #e0cb52;
		border-color: var(--example-border);
		background: #fcfaee;
		background: var(--example-bg);
		color: black;
		color: var(--example-text);
		counter-increment: example;
		overflow: auto;
		clear: both;
	}
	.example::before, .example > .marker {
		color: #574b0f;
		color: var(--exampleheading-text);
	}
	/* Add .example::before { content: "Example " counter(example) " "; } for autogen numbers,
	  or use class="marker" to mark up the example number in source. */

/** Non-normative Note ********************************************************/

	.note {
		border-color: #52e052;
		border-color: var(--note-border);
		background: #e9fbe9;
		background: var(--note-bg);
		color: black;
		color: var(--note-text);
		overflow: auto;
	}

	.note::before, .note > .marker,
	details.note > summary {
		color: hsl(120, 70%, 30%);
		color: var(--noteheading-text);
	}
	/* Add .note::before { content: "Note "; } for autogen label,
	  or use class="marker" to mark up the label in source. */

	details.note[open] > summary {
		border-bottom: 1px silver solid;
		border-bottom: 1px var(--notesummary-underline) solid;
	}

/** Assertion Box *************************************************************/
	/*  for assertions in algorithms */

	.assertion {
		border-color: #AAA;
		border-color: var(--assertion-border);
		background: #EEE;
		background: var(--assertion-bg);
		color: black;
		color: var(--assertion-text);
	}

/** Advisement Box ************************************************************/
	/*  for attention-grabbing normative statements */

	.advisement {
		border-color: orange;
		border-color: var(--advisement-border);
		border-style: none solid;
		background: #fec;
		background: var(--advisement-bg);
		color: black;
		color: var(--advisement-text);
	}
	strong.advisement {
		display: block;
		text-align: center;
	}
	.advisement::before, .advisement > .marker {
		color: #b35f00;
		color: var(--advisementheading-text);
	}

/** Amendment Box *************************************************************/

	.amendment, .correction, .addition {
		border-color: #330099;
		border-color: var(--amendment-border);
		background: #F5F0FF;
		background: var(--amendment-bg);
		color: black;
		color: var(--amendment-text);
	}
	.amendment.proposed, .correction.proposed, .addition.proposed {
		border-style: solid;
		border-block-width: 0.25em;
	}
	.amendment::before, .amendment > .marker,
	details.amendment > summary::before, details.amendment > summary > .marker,
	.correction::before, .correction > .marker,
	details.correction > summary::before, details.correction > summary > .marker,
	.addition::before, .addition > .marker,
	details.addition > summary::before, details.addition > summary > .marker {
		color: #220066;
		color: var(--amendmentheading-text);
	}
	.amendment.proposed::before, .amendment.proposed > .marker,
	details.amendment.proposed > summary::before, details.amendment.proposed > summary > .marker,
	.correction.proposed::before, .correction.proposed > .marker,
	details.correction.proposed > summary::before, details.correction.proposed > summary > .marker,
	.addition.proposed::before, .addition.proposed > .marker,
	details.addition.proposed > summary::before, details.addition.proposed > summary > .marker {
		font-weight: bold;
	}

/** Spec Obsoletion Notice ****************************************************/
	/* obnoxious obsoletion notice for older/abandoned specs. */

	details {
		display: block;
	}
	summary {
		font-weight: bolder;
	}

	.annoying-warning:not(details),
	details.annoying-warning:not([open]) > summary,
	details.annoying-warning[open] {
		background: hsla(40,100%,50%,0.95);
		background: var(--warning-bg);
		color: black;
		color: var(--warning-text);
		padding: .75em 1em;
		border: red;
		border: var(--warning-border);
		border-style: solid none;
		box-shadow: 0 2px 8px black;
		text-align: center;
	}
	.annoying-warning :last-child {
		margin-bottom: 0;
	}

@media not print {
	details.annoying-warning[open] {
		position: fixed;
		left: 0;
		right: 0;
		bottom: 2em;
		z-index: 1000;
	}
}

	details.annoying-warning:not([open]) > summary {
		text-align: center;
	}

/** Entity Definition Boxes ***************************************************/

	.def {
		padding: .5em 1em;
		background: #def;
		background: var(--def-bg);
		margin: 1.2em 0;
		border-left: 0.5em solid #8ccbf2;
		border-left: 0.5em solid var(--def-border);
		color: black;
		color: var(--def-text);
	}

/******************************************************************************/
/*                                    Tables                                  */
/******************************************************************************/

	th, td {
		text-align: left;
		text-align: start;
	}

/** Property/Descriptor Definition Tables *************************************/

	table.def {
		/* inherits .def box styling, see above */
		width: 100%;
		border-spacing: 0;
	}

	table.def td,
	table.def th {
		padding: 0.5em;
		vertical-align: baseline;
		border-bottom: 1px solid #bbd7e9;
		border-bottom: 1px solid var(--defrow-border);
	}

	table.def > tbody > tr:last-child th,
	table.def > tbody > tr:last-child td {
		border-bottom: 0;
	}

	table.def th {
		font-style: italic;
		font-weight: normal;
		padding-left: 1em;
		width: 3em;
	}

	/* For when values are extra-complex and need formatting for readability */
	table td.pre {
		white-space: pre-wrap;
	}

	/* A footnote at the bottom of a def table */
	table.def td.footnote {
		padding-top: 0.6em;
	}
	table.def td.footnote::before {
		content: " ";
		display: block;
		height: 0.6em;
		width: 4em;
		border-top: thin solid;
	}

/** Data tables (and properly marked-up index tables) *************************/
	/*
		<table class="data"> highlights structural relationships in a table
		when correct markup is used (e.g. thead/tbody, th vs. td, scope attribute)

		Use class="complex data" for particularly complicated tables --
		(This will draw more lines: busier, but clearer.)

		Use class="long" on table cells with paragraph-like contents
		(This will adjust text alignment accordingly.)
		Alternately use class="longlastcol" on tables, to have the last column assume "long".
	*/

	table {
		word-wrap: normal;
		overflow-wrap: normal;
		hyphens: manual;
	}

	table.data,
	table.index {
		margin: 1em auto;
		border-collapse: collapse;
		border: hidden;
		width: 100%;
	}
	table.data caption,
	table.index caption {
		max-width: 50em;
		margin: 0 auto 1em;
	}

	table.data td,  table.data th,
	table.index td, table.index th {
		padding: 0.5em 1em;
		border-width: 1px;
		border-color: silver;
		border-color: var(--datacell-border);
		border-top-style: solid;
	}

	table.data thead td:empty {
		padding: 0;
		border: 0;
	}

	table.data  thead,
	table.index thead,
	table.data  tbody,
	table.index tbody {
		border-bottom: 2px solid;
	}

	table.data colgroup,
	table.index colgroup {
		border-left: 2px solid;
	}

	table.data  tbody th:first-child,
	table.index tbody th:first-child  {
		border-right: 2px solid;
		border-top: 1px solid silver;
		border-top: 1px solid var(--datacell-border);
		padding-right: 1em;
	}

	table.data th[colspan],
	table.data td[colspan] {
		text-align: center;
	}

	table.complex.data th,
	table.complex.data td {
		border: 1px solid silver;
		border: 1px solid var(--datacell-border);
		text-align: center;
	}

	table.data.longlastcol td:last-child,
	table.data td.long {
		vertical-align: baseline;
		text-align: left;
	}

	table.data img {
		vertical-align: middle;
	}


/*
Alternate table alignment rules

	table.data,
	table.index {
		text-align: center;
	}

	table.data  thead th[scope="row"],
	table.index thead th[scope="row"] {
		text-align: right;
	}

	table.data  tbody th:first-child,
	table.index tbody th:first-child  {
		text-align: right;
	}

Possible extra rowspan handling

	table.data  tbody th[rowspan]:not([rowspan='1']),
	table.index tbody th[rowspan]:not([rowspan='1']),
	table.data  tbody td[rowspan]:not([rowspan='1']),
	table.index tbody td[rowspan]:not([rowspan='1']) {
		border-left: 1px solid silver;
	}

	table.data  tbody th[rowspan]:first-child,
	table.index tbody th[rowspan]:first-child,
	table.data  tbody td[rowspan]:first-child,
	table.index tbody td[rowspan]:first-child{
		border-left: 0;
		border-right: 1px solid silver;
	}
*/

/******************************************************************************/
/*                                  Indices                                   */
/******************************************************************************/


/** Table of Contents *********************************************************/

	.toc a {
		/* More spacing; use padding to make it part of the click target. */
		padding: 0.1rem 1px 0;
		/* Larger, more consistently-sized click target */
		display: block;
		/* Switch to using border-bottom for underlines */
		text-decoration: none;
		border-bottom: 1px solid;
		/* Reverse color scheme */
		color: black;
		color: var(--toclink-text);
		border-color: #3980b5;
		border-color: var(--toclink-underline);
	}
	.toc a:visited {
		color: black;
		color: var(--toclink-visited-text);
		border-color: #054572;
		border-color: var(--toclink-visited-underline);
	}
	.toc a:focus,
	.toc a:hover {
		background: rgba(75%, 75%, 75%, .25);
		background: var(--a-hover-bg);
		border-bottom-width: 3px;
		margin-bottom: -2px;
	}
	.toc a:not(:focus):not(:hover) {
		/* Allow colors to cascade through from link styling */
		border-bottom-color: transparent;
	}

	.toc, .toc ol, .toc ul, .toc li {
		list-style: none; /* Numbers must be inlined into source */
		/* because generated content isn't search/selectable and markers can't do multilevel yet */
		margin:  0;
		padding: 0;
	}
	.toc {
		line-height: 1.1em;
	}

	/* ToC not indented until third level, but font style & margins show hierarchy */
	.toc > li			{ font-weight: bold;   }
	.toc > li li		 { font-weight: normal; }
	.toc > li li li	  { font-size:   95%;	}
	.toc > li li li li	{ font-size:   90%;	}
	.toc > li li li li li { font-size:   85%;	}

	/* @supports not (display:grid) { */
		.toc > li			{ margin: 1.5rem 0;	}
		.toc > li li		 { margin: 0.3rem 0;	}
		.toc > li li li	  { margin-left: 2rem;   }

		/* Section numbers in a column of their own */
		.toc .secno {
			float: left;
			width: 4rem;
			white-space: nowrap;
		}
		.toc > li li li li .secno { font-size: 85%; }
		.toc > li li li li li .secno { font-size: 100%; }

		.toc li {
			clear: both;
		}

		:not(li) > .toc			 { margin-left:  5rem; }
		.toc .secno				 { margin-left: -5rem; }
		.toc > li li li .secno	  { margin-left: -7rem; }
		.toc > li li li li .secno	{ margin-left: -9rem; }
		.toc > li li li li li .secno { margin-left: -11rem; }

		/* Tighten up indentation in narrow ToCs */
		@media (max-width: 30em) {
			:not(li) > .toc			 { margin-left:  4rem; }
			.toc .secno				 { margin-left: -4rem; }
			.toc > li li li			 { margin-left:  1rem; }
			.toc > li li li .secno	  { margin-left: -5rem; }
			.toc > li li li li .secno	{ margin-left: -6rem; }
			.toc > li li li li li .secno { margin-left: -7rem; }
		}
		/* Loosen it on wide screens */
		@media screen and (min-width: 78em) {
			body:not(.toc-inline) :not(li) > .toc			 { margin-left:  4rem; }
			body:not(.toc-inline) .toc .secno				 { margin-left: -4rem; }
			body:not(.toc-inline) .toc > li li li			 { margin-left:  1rem; }
			body:not(.toc-inline) .toc > li li li .secno	  { margin-left: -5rem; }
			body:not(.toc-inline) .toc > li li li li .secno	{ margin-left: -6rem; }
			body:not(.toc-inline) .toc > li li li li li .secno { margin-left: -7rem; }
	}
	/* } */

	@supports (display:grid) and (display:contents) {
		/* Use #toc over .toc to override non-@supports rules. */
		#toc {
			display: grid;
			align-content: start;
			grid-template-columns: auto 1fr;
			grid-column-gap: 1rem;
			column-gap: 1rem;
			grid-row-gap: .6rem;
			row-gap: .6rem;
		}
		#toc h2 {
			grid-column: 1 / -1;
			margin-bottom: 0;
		}
		#toc ol,
		#toc li,
		#toc a {
			display: contents;
			/* Switch <a> to subgrid when supported */
		}
		#toc span {
			margin: 0;
		}
		#toc > .toc > li > a > span {
			/* The spans of the top-level list,
			  comprising the first items of each top-level section. */
			margin-top: 1.1rem;
		}
		#toc#toc .secno { /* Ugh, need more specificity to override base.css */
			grid-column: 1;
			width: auto;
			margin-left: 0;
		}
		#toc .content {
			grid-column: 2;
			width: auto;
			margin-right: 1rem;
			border-bottom: 3px solid transparent;
			margin-bottom: -3px;
		}
		#toc .content:hover,
		#toc .content:focus {
			background: rgba(75%, 75%, 75%, .25);
			background: var(--a-hover-bg);
			border-bottom-color: #054572;
			border-bottom-color: var(--toclink-underline);
		}
		#toc li li li .content {
			margin-left: 1rem;
		}
		#toc li li li li .content {
			margin-left: 2rem;
		}
	}


/** Index *********************************************************************/

	/* Index Lists: Layout */
	ul.index	  { margin-left: 0; columns: 15em; text-indent: 1em hanging; }
	ul.index li	{ margin-left: 0; list-style: none; break-inside: avoid; }
	ul.index li li { margin-left: 1em; }
	ul.index dl	{ margin-top: 0; }
	ul.index dt	{ margin: .2em 0 .2em 20px;}
	ul.index dd	{ margin: .2em 0 .2em 40px;}
	/* Index Lists: Typography */
	ul.index ul,
	ul.index dl { font-size: smaller; }
	@media not print {
		ul.index li a + span {
			white-space: nowrap;
			color: transparent; }
		ul.index li a:hover + span,
		ul.index li a:focus + span {
			color: #707070;
			color: var(--indexinfo-text);
		}
	}

/** Index Tables *****************************************************/
	/* See also the data table styling section, which this effectively subclasses */

	table.index {
		font-size: small;
		border-collapse: collapse;
		border-spacing: 0;
		text-align: left;
		margin: 1em 0;
	}

	table.index td,
	table.index th {
		padding: 0.4em;
	}

	table.index tr:hover td:not([rowspan]),
	table.index tr:hover th:not([rowspan]) {
		color: black;
		color: var(--indextable-hover-text);
		background: #f7f8f9;
		background: var(--indextable-hover-bg);
	}

	/* The link in the first column in the property table (formerly a TD) */
	table.index th:first-child a {
		font-weight: bold;
	}

/** Outdated warning **********************************************************/

.outdated-spec {
	color: black;
	color: var(--outdatedspec-text);
	background-color: rgba(0,0,0,0.5);
	background-color: var(--outdatedspec-bg);
}

.outdated-warning {
	position: fixed;
	bottom: 50%;
	left: 0;
	right: 0;
	margin: 0 auto;
	width: 50%;
	background: maroon;
	background: var(--outdated-bg);
	color: white;
	color: var(--outdated-text);
	border-radius: 1em;
	box-shadow: 0 0 1em red;
	box-shadow: 0 0 1em var(--outdated-shadow);
	padding: 2em;
	text-align: center;
	z-index: 2;
}

.outdated-warning a {
	color: currentcolor;
	background: transparent;
}

.edited-rec-warning {
	background: darkorange;
	background: var(--editedrec-bg);
	box-shadow: 0 0 1em;
}

.outdated-warning button {
	color: var(--outdated-text);
	border-radius: 1em;
	box-shadow: 0 0 1em red;
	box-shadow: 0 0 1em var(--outdated-shadow);
	padding: 2em;
	text-align: center;
	z-index: 2;
}

.outdated-warning a {
	color: currentcolor;
	background: transparent;
}

.edited-rec-warning {
	background: darkorange;
	background: var(--editedrec-bg);
	box-shadow: 0 0 1em;
}

.outdated-warning button {
	position: absolute;
	top: 0;
	right:0;
	margin: 0;
	border: 0;
	padding: 0.25em 0.5em;
	background: transparent;
	color: white;
	color: var(--outdated-text);
	font:1em sans-serif;
	text-align:center;
}

.outdated-warning span {
	display: block;
}

.outdated-collapsed {
	bottom: 0;
	border-radius: 0;
	width: 100%;
	padding: 0;
}

/******************************************************************************/
/*                                    Print                                   */
/******************************************************************************/

	@media print {
		/* Pages have their own margins. */
		html {
			margin: 0;
		}
		/* Serif for print. */
		body {
			font-family: serif;
		}

		.outdated-warning {
			position: absolute;
			border-style: solid;
			border-color: red;
		}

		.outdated-warning input {
			display: none;
		}
	}
	@page {
		margin: 1.5cm 1.1cm;
	}



/******************************************************************************/
/*                             Overflow Control                               */
/******************************************************************************/

	.figure .caption, .sidefigure .caption, figcaption {
		/* in case figure is overlarge, limit caption to 50em */
		max-width: 50rem;
		margin-left: auto;
		margin-right: auto;
	}
	.overlarge {
		/* Magic to create good item positioning:
		  "content column" is 50ems wide at max; less on smaller screens.
		  Extra space (after ToC + content) is empty on the right.

		  1. When item < content column, centers item in column.
		  2. When content < item < available, left-aligns.
		  3. When item > available, fills available + scroll bar.
		*/
		display: grid;
		grid-template-columns: minmax(0, 50em);
	}
	.overlarge > table {
		/* limit preferred width of table */
		max-width: 50em;
		margin-left: auto;
		margin-right: auto;
	}

	@media (min-width: 55em) {
		.overlarge {
			margin-right: calc(13px + 26.5rem - 50vw);
			max-width: none;
		}
	}
	@media screen and (min-width: 78em) {
		body:not(.toc-inline) .overlarge {
			/* 30.5em body padding 50em content area */
			margin-right: calc(40em - 50vw) !important;
		}
	}
	@media screen and (min-width: 90em) {
		body:not(.toc-inline) .overlarge {
			/* 4em html margin 30.5em body padding 50em content area */
			margin-right: calc(84.5em - 100vw) !important;
		}
	}

	@media not print {
		.overlarge {
			overflow-x: auto;
			/* See Lea Verou's explanation background-attachment:
			* http://lea.verou.me/2012/04/background-attachment-local/
			*
			background: top left  / 4em 100% linear-gradient(to right,  #ffffff, rgba(255, 255, 255, 0)) local,
						top right / 4em 100% linear-gradient(to left, #ffffff, rgba(255, 255, 255, 0)) local,
						top left  / 1em 100% linear-gradient(to right,  #c3c3c5, rgba(195, 195, 197, 0)) scroll,
						top right / 1em 100% linear-gradient(to left, #c3c3c5, rgba(195, 195, 197, 0)) scroll,
						white;
			background-repeat: no-repeat;
			*/
		}
	}
</style>
<style>
    table, th, td {
      border: 1px solid black;
      border-collapse: collapse;
      vertical-align: top;
    }
    th, td {
      border-left: none;
      border-right: none;
      padding: 0px 10px;
    }
    th {
      text-align: center;
    }

    del { background: #fcc; color: #000; text-decoration: line-through; }
    ins { background: #cfc; color: #000; }
    blockquote .highlight:not(.idl) { background: initial; margin: initial; padding: 0.5em }
    blockquote ul { background: inherit; }
    blockquote code.highlight:not(.idl) { padding: initial; }
    blockquote c-[a] { color: inherit; } /* Keyword.Declaration */
    blockquote c-[b] { color: inherit; } /* Keyword.Type */
    blockquote c-[c] { color: inherit; } /* Comment */
    blockquote c-[d] { color: inherit; } /* Comment.Multiline */
    blockquote c-[e] { color: inherit; } /* Name.Attribute */
    blockquote c-[f] { color: inherit; } /* Name.Tag */
    blockquote c-[g] { color: inherit; } /* Name.Variable */
    blockquote c-[k] { color: inherit; } /* Keyword */
    blockquote c-[l] { color: inherit; } /* Literal */
    blockquote c-[m] { color: inherit; } /* Literal.Number */
    blockquote c-[n] { color: inherit; } /* Name */
    blockquote c-[o] { color: inherit; } /* Operator */
    blockquote c-[p] { color: inherit; } /* Punctuation */
    blockquote c-[s] { color: inherit; } /* Literal.String */
    blockquote c-[t] { color: inherit; } /* Literal.String.Single */
    blockquote c-[u] { color: inherit; } /* Literal.String.Double */
    blockquote c-[cp] { color: inherit; } /* Comment.Preproc */
    blockquote c-[c1] { color: inherit; } /* Comment.Single */
    blockquote c-[cs] { color: inherit; } /* Comment.Special */
    blockquote c-[kc] { color: inherit; } /* Keyword.Constant */
    blockquote c-[kn] { color: inherit; } /* Keyword.Namespace */
    blockquote c-[kp] { color: inherit; } /* Keyword.Pseudo */
    blockquote c-[kr] { color: inherit; } /* Keyword.Reserved */
    blockquote c-[ld] { color: inherit; } /* Literal.Date */
    blockquote c-[nc] { color: inherit; } /* Name.Class */
    blockquote c-[no] { color: inherit; } /* Name.Constant */
    blockquote c-[nd] { color: inherit; } /* Name.Decorator */
    blockquote c-[ni] { color: inherit; } /* Name.Entity */
    blockquote c-[ne] { color: inherit; } /* Name.Exception */
    blockquote c-[nf] { color: inherit; } /* Name.Function */
    blockquote c-[nl] { color: inherit; } /* Name.Label */
    blockquote c-[nn] { color: inherit; } /* Name.Namespace */
    blockquote c-[py] { color: inherit; } /* Name.Property */
    blockquote c-[ow] { color: inherit; } /* Operator.Word */
    blockquote c-[mb] { color: inherit; } /* Literal.Number.Bin */
    blockquote c-[mf] { color: inherit; } /* Literal.Number.Float */
    blockquote c-[mh] { color: inherit; } /* Literal.Number.Hex */
    blockquote c-[mi] { color: inherit; } /* Literal.Number.Integer */
    blockquote c-[mo] { color: inherit; } /* Literal.Number.Oct */
    blockquote c-[sb] { color: inherit; } /* Literal.String.Backtick */
    blockquote c-[sc] { color: inherit; } /* Literal.String.Char */
    blockquote c-[sd] { color: inherit; } /* Literal.String.Doc */
    blockquote c-[se] { color: inherit; } /* Literal.String.Escape */
    blockquote c-[sh] { color: inherit; } /* Literal.String.Heredoc */
    blockquote c-[si] { color: inherit; } /* Literal.String.Interpol */
    blockquote c-[sx] { color: inherit; } /* Literal.String.Other */
    blockquote c-[sr] { color: inherit; } /* Literal.String.Regex */
    blockquote c-[ss] { color: inherit; } /* Literal.String.Symbol */
    blockquote c-[vc] { color: inherit; } /* Name.Variable.Class */
    blockquote c-[vg] { color: inherit; } /* Name.Variable.Global */
    blockquote c-[vi] { color: inherit; } /* Name.Variable.Instance */
    blockquote c-[il] { color: inherit; } /* Literal.Number.Integer.Long */
  </style>
  <meta content="Bikeshed version 82ce88815, updated Thu Sep 7 16:33:55 2023 -0700" name="generator">
  <link href="https://wg21.link/P3020" rel="canonical">
  <link href="https://isocpp.org/favicon.ico" rel="icon">
<style>/* Boilerplate: style-autolinks */
.css.css, .property.property, .descriptor.descriptor {
    color: var(--a-normal-text);
    font-size: inherit;
    font-family: inherit;
}
.css::before, .property::before, .descriptor::before {
    content: "‘";
}
.css::after, .property::after, .descriptor::after {
    content: "’";
}
.property, .descriptor {
    /* Don't wrap property and descriptor names */
    white-space: nowrap;
}
.type { /* CSS value <type> */
    font-style: italic;
}
pre .property::before, pre .property::after {
    content: "";
}
[data-link-type="property"]::before,
[data-link-type="propdesc"]::before,
[data-link-type="descriptor"]::before,
[data-link-type="value"]::before,
[data-link-type="function"]::before,
[data-link-type="at-rule"]::before,
[data-link-type="selector"]::before,
[data-link-type="maybe"]::before {
    content: "‘";
}
[data-link-type="property"]::after,
[data-link-type="propdesc"]::after,
[data-link-type="descriptor"]::after,
[data-link-type="value"]::after,
[data-link-type="function"]::after,
[data-link-type="at-rule"]::after,
[data-link-type="selector"]::after,
[data-link-type="maybe"]::after {
    content: "’";
}

[data-link-type].production::before,
[data-link-type].production::after,
.prod [data-link-type]::before,
.prod [data-link-type]::after {
    content: "";
}

[data-link-type=element],
[data-link-type=element-attr] {
    font-family: Menlo, Consolas, "DejaVu Sans Mono", monospace;
    font-size: .9em;
}
[data-link-type=element]::before { content: "<" }
[data-link-type=element]::after  { content: ">" }

[data-link-type=biblio] {
    white-space: pre;
}

@media (prefers-color-scheme: dark) {
    :root {
        --selflink-text: black;
        --selflink-bg: silver;
        --selflink-hover-text: white;
    }
}
</style>
<style>/* Boilerplate: style-colors */

/* Any --*-text not paired with a --*-bg is assumed to have a transparent bg */
:root {
    color-scheme: light dark;

    --text: black;
    --bg: white;

    --unofficial-watermark: url(https://www.w3.org/StyleSheets/TR/2016/logos/UD-watermark);

    --logo-bg: #1a5e9a;
    --logo-active-bg: #c00;
    --logo-text: white;

    --tocnav-normal-text: #707070;
    --tocnav-normal-bg: var(--bg);
    --tocnav-hover-text: var(--tocnav-normal-text);
    --tocnav-hover-bg: #f8f8f8;
    --tocnav-active-text: #c00;
    --tocnav-active-bg: var(--tocnav-normal-bg);

    --tocsidebar-text: var(--text);
    --tocsidebar-bg: #f7f8f9;
    --tocsidebar-shadow: rgba(0,0,0,.1);
    --tocsidebar-heading-text: hsla(203,20%,40%,.7);

    --toclink-text: var(--text);
    --toclink-underline: #3980b5;
    --toclink-visited-text: var(--toclink-text);
    --toclink-visited-underline: #054572;

    --heading-text: #005a9c;

    --hr-text: var(--text);

    --algo-border: #def;

    --del-text: red;
    --del-bg: transparent;
    --ins-text: #080;
    --ins-bg: transparent;

    --a-normal-text: #034575;
    --a-normal-underline: #bbb;
    --a-visited-text: var(--a-normal-text);
    --a-visited-underline: #707070;
    --a-hover-bg: rgba(75%, 75%, 75%, .25);
    --a-active-text: #c00;
    --a-active-underline: #c00;

    --blockquote-border: silver;
    --blockquote-bg: transparent;
    --blockquote-text: currentcolor;

    --issue-border: #e05252;
    --issue-bg: #fbe9e9;
    --issue-text: var(--text);
    --issueheading-text: #831616;

    --example-border: #e0cb52;
    --example-bg: #fcfaee;
    --example-text: var(--text);
    --exampleheading-text: #574b0f;

    --note-border: #52e052;
    --note-bg: #e9fbe9;
    --note-text: var(--text);
    --noteheading-text: hsl(120, 70%, 30%);
    --notesummary-underline: silver;

    --assertion-border: #aaa;
    --assertion-bg: #eee;
    --assertion-text: black;

    --advisement-border: orange;
    --advisement-bg: #fec;
    --advisement-text: var(--text);
    --advisementheading-text: #b35f00;

    --warning-border: red;
    --warning-bg: hsla(40,100%,50%,0.95);
    --warning-text: var(--text);

    --amendment-border: #330099;
    --amendment-bg: #F5F0FF;
    --amendment-text: var(--text);
    --amendmentheading-text: #220066;

    --def-border: #8ccbf2;
    --def-bg: #def;
    --def-text: var(--text);
    --defrow-border: #bbd7e9;

    --datacell-border: silver;

    --indexinfo-text: #707070;

    --indextable-hover-text: black;
    --indextable-hover-bg: #f7f8f9;

    --outdatedspec-bg: rgba(0, 0, 0, .5);
    --outdatedspec-text: black;
    --outdated-bg: maroon;
    --outdated-text: white;
    --outdated-shadow: red;

    --editedrec-bg: darkorange;
}

@media (prefers-color-scheme: dark) {
    :root {
        --text: #ddd;
        --bg: black;

        --unofficial-watermark: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='400' height='400'%3E%3Cg fill='%23100808' transform='translate(200 200) rotate(-45) translate(-200 -200)' stroke='%23100808' stroke-width='3'%3E%3Ctext x='50%25' y='220' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EUNOFFICIAL%3C/text%3E%3Ctext x='50%25' y='305' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EDRAFT%3C/text%3E%3C/g%3E%3C/svg%3E");

        --logo-bg: #1a5e9a;
        --logo-active-bg: #c00;
        --logo-text: white;

        --tocnav-normal-text: #999;
        --tocnav-normal-bg: var(--bg);
        --tocnav-hover-text: var(--tocnav-normal-text);
        --tocnav-hover-bg: #080808;
        --tocnav-active-text: #f44;
        --tocnav-active-bg: var(--tocnav-normal-bg);

        --tocsidebar-text: var(--text);
        --tocsidebar-bg: #080808;
        --tocsidebar-shadow: rgba(255,255,255,.1);
        --tocsidebar-heading-text: hsla(203,20%,40%,.7);

        --toclink-text: var(--text);
        --toclink-underline: #6af;
        --toclink-visited-text: var(--toclink-text);
        --toclink-visited-underline: #054572;

        --heading-text: #8af;

        --hr-text: var(--text);

        --algo-border: #456;

        --del-text: #f44;
        --del-bg: transparent;
        --ins-text: #4a4;
        --ins-bg: transparent;

        --a-normal-text: #6af;
        --a-normal-underline: #555;
        --a-visited-text: var(--a-normal-text);
        --a-visited-underline: var(--a-normal-underline);
        --a-hover-bg: rgba(25%, 25%, 25%, .2);
        --a-active-text: #f44;
        --a-active-underline: var(--a-active-text);

        --borderedblock-bg: rgba(255, 255, 255, .05);

        --blockquote-border: silver;
        --blockquote-bg: var(--borderedblock-bg);
        --blockquote-text: currentcolor;

        --issue-border: #e05252;
        --issue-bg: var(--borderedblock-bg);
        --issue-text: var(--text);
        --issueheading-text: hsl(0deg, 70%, 70%);

        --example-border: hsl(50deg, 90%, 60%);
        --example-bg: var(--borderedblock-bg);
        --example-text: var(--text);
        --exampleheading-text: hsl(50deg, 70%, 70%);

        --note-border: hsl(120deg, 100%, 35%);
        --note-bg: var(--borderedblock-bg);
        --note-text: var(--text);
        --noteheading-text: hsl(120, 70%, 70%);
        --notesummary-underline: silver;

        --assertion-border: #444;
        --assertion-bg: var(--borderedblock-bg);
        --assertion-text: var(--text);

        --advisement-border: orange;
        --advisement-bg: #222218;
        --advisement-text: var(--text);
        --advisementheading-text: #f84;

        --warning-border: red;
        --warning-bg: hsla(40,100%,20%,0.95);
        --warning-text: var(--text);

        --amendment-border: #330099;
        --amendment-bg: #080010;
        --amendment-text: var(--text);
        --amendmentheading-text: #cc00ff;

        --def-border: #8ccbf2;
        --def-bg: #080818;
        --def-text: var(--text);
        --defrow-border: #136;

        --datacell-border: silver;

        --indexinfo-text: #aaa;

        --indextable-hover-text: var(--text);
        --indextable-hover-bg: #181818;

        --outdatedspec-bg: rgba(255, 255, 255, .5);
        --outdatedspec-text: black;
        --outdated-bg: maroon;
        --outdated-text: white;
        --outdated-shadow: red;

        --editedrec-bg: darkorange;
    }
    /* In case a transparent-bg image doesn't expect to be on a dark bg,
       which is quite common in practice... */
    img { background: white; }
}
</style>
<style>/* Boilerplate: style-counters */
body {
    counter-reset: example figure issue;
}
.issue {
    counter-increment: issue;
}
.issue:not(.no-marker)::before {
    content: "Issue " counter(issue);
}

.example {
    counter-increment: example;
}
.example:not(.no-marker)::before {
    content: "Example " counter(example);
}
.invalid.example:not(.no-marker)::before,
.illegal.example:not(.no-marker)::before {
    content: "Invalid Example" counter(example);
}

figcaption {
    counter-increment: figure;
}
figcaption:not(.no-marker)::before {
    content: "Figure " counter(figure) " ";
}
</style>
<style>/* Boilerplate: style-issues */
a[href].issue-return {
    float: right;
    float: inline-end;
    color: var(--issueheading-text);
    font-weight: bold;
    text-decoration: none;
}
</style>
<style>/* Boilerplate: style-md-lists */
/* This is a weird hack for me not yet following the commonmark spec
   regarding paragraph and lists. */
[data-md] > :first-child {
    margin-top: 0;
}
[data-md] > :last-child {
    margin-bottom: 0;
}
</style>
<style>/* Boilerplate: style-selflinks */

:root {
    --selflink-text: white;
    --selflink-bg: gray;
    --selflink-hover-text: black;
}
.heading, .issue, .note, .example, li, dt {
    position: relative;
}
a.self-link {
    position: absolute;
    top: 0;
    left: calc(-1 * (3.5rem - 26px));
    width: calc(3.5rem - 26px);
    height: 2em;
    text-align: center;
    border: none;
    transition: opacity .2s;
    opacity: .5;
}
a.self-link:hover {
    opacity: 1;
}
.heading > a.self-link {
    font-size: 83%;
}
.example > a.self-link,
.note > a.self-link,
.issue > a.self-link {
    /* These blocks are overflow:auto, so positioning outside
       doesn't work. */
    left: auto;
    right: 0;
}
li > a.self-link {
    left: calc(-1 * (3.5rem - 26px) - 2em);
}
dfn > a.self-link {
    top: auto;
    left: auto;
    opacity: 0;
    width: 1.5em;
    height: 1.5em;
    background: var(--selflink-bg);
    color: var(--selflink-text);
    font-style: normal;
    transition: opacity .2s, background-color .2s, color .2s;
}
dfn:hover > a.self-link {
    opacity: 1;
}
dfn > a.self-link:hover {
    color: var(--selflink-hover-text);
}

a.self-link::before            { content: "¶"; }
.heading > a.self-link::before { content: "§"; }
dfn > a.self-link::before      { content: "#"; }
</style>
 <body class="h-entry">
  <div class="head">
   <p data-fill-with="logo"></p>
   <h1 class="p-name no-ref" id="title">P3020R0<br>2023-09 Library Evolution Poll Outcomes</h1>
   <h2 class="no-num no-toc no-ref heading settled" id="profile-and-date"><span class="content">Published Proposal, <time class="dt-updated" datetime="2023-10-15">2023-10-15</time></span></h2>
   <div data-fill-with="spec-metadata">
    <dl>
     <dt class="editor">Authors:
     <dd class="editor p-author h-card vcard"><a class="p-name fn u-email email" href="mailto:sinbal2l@gmail.com">Inbal Levi - Library Evolution Chair</a> (<span class="p-org org">MPGC Services LTD</span>)
     <dd class="editor p-author h-card vcard"><a class="p-name fn u-email email" href="mailto:fabio@fracassi.de">Fabio Fracassi - Library Evolution Assistant Chair</a> (<span class="p-org org">CODE University of Applied Sciences</span>)
     <dd class="editor p-author h-card vcard"><a class="p-name fn u-email email" href="mailto:ben.craig@gmail.com">Ben Craig - Library Evolution Assistant Chair</a> (<span class="p-org org">Raven</span>)
     <dd class="editor p-author h-card vcard"><a class="p-name fn u-email email" href="mailto:billy.baker.cpp@gmail.com">Billy Baker - Library Evolution Incubator Chair</a> (<span class="p-org org">NVIDIA</span>)
     <dd class="editor p-author h-card vcard"><a class="p-name fn u-email email" href="mailto:nevin@cplusplusguy.com">Nevin Liber - Library Evolution Incubator Assistant Chair and Admin Chair</a> (<span class="p-org org">Argonne National Laboratory</span>)
     <dd class="editor p-author h-card vcard"><a class="p-name fn u-email email" href="mailto:corentin.jabot@gmail.com">Corentin Jabot - Library Mailing List Review Manager</a>
     <dt>Source:
     <dd><a href="https://github.com/inbal2l/wg21_library_evolution_polls_outcome_script/blob/main/2023_09_library_evolution_poll_outcomes.bs">GitHub</a>
     <dt>Project:
     <dd>ISO/IEC 14882 Programming Languages — C++, ISO/IEC JTC1/SC22/WG21
     <dt>Audience:
     <dd>WG21
    </dl>
   </div>
   <div data-fill-with="warning"></div>
   <hr title="Separator for header">
  </div>
  <nav data-fill-with="table-of-contents" id="toc">
   <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
   <ol class="toc" role="directory">
    <li><a href="#introduction"><span class="secno">1</span> <span class="content">Introduction</span></a>
    <li><a href="#poll-outcomes"><span class="secno">2</span> <span class="content">Poll Outcomes</span></a>
    <li>
     <a href="#poll-comments"><span class="secno">3</span> <span class="content">Selected Poll Comments</span></a>
     <ol class="toc">
      <li><a href="#poll-1-send-p0843r9-inplace_vector-to-library-working-group-for-c26"><span class="secno">3.1</span> <span class="content">Poll 1: Send "<span title="inplace_vector">[P0843R9]</span> <code class="highlight"><c- n>inplace_vector</c-></code>" to Library Working Group for C++26.</span></a>
      <li><a href="#poll-2-send-p1068r9-vector-api-for-random-number-generation-to-library-working-group-for-c26"><span class="secno">3.2</span> <span class="content">Poll 2: Send "<span title="Vector API for random number generation">[P1068R9]</span> Vector API for random number generation" to Library Working Group for C++26.</span></a>
      <li><a href="#poll-3-send-p2447r4-stdspan-over-an-initializer-list-to-library-working-group-for-c26"><span class="secno">3.3</span> <span class="content">Poll 3: Send "<span title="std::span over an initializer list">[P2447R4]</span> <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>span</c-></code> over an initializer list" to Library Working Group for C++26.</span></a>
      <li><a href="#poll-4-send-p2591r4-concatenation-of-strings-and-string-views-to-library-working-group-for-c26"><span class="secno">3.4</span> <span class="content">Poll 4: Send "<span title="Concatenation of strings and string views">[P2591R4]</span> Concatenation of strings and string views" to Library Working Group for C++26.</span></a>
      <li><a href="#poll-5-send-p2819r1-add-tuple-protocol-to-complex-to-library-working-group-for-c26"><span class="secno">3.5</span> <span class="content">Poll 5: Send "<span title="Add tuple protocol to complex">[P2819R1]</span> Add tuple protocol to complex" to Library Working Group for C++26.</span></a>
      <li><a href="#poll-6-send-p2821r4-spanat-to-library-working-group-for-c26"><span class="secno">3.6</span> <span class="content">Poll 6: Send "<span title="span.at()">[P2821R4]</span> <code class="highlight"><c- n>span</c-><c- p>.</c-><c- n>at</c-><c- p>()</c-></code>" to Library Working Group for C++26.</span></a>
      <li><a href="#poll-7-send-p2833r1-freestanding-library-inout-expected-span-to-library-working-group-for-c26"><span class="secno">3.7</span> <span class="content">Poll 7: Send "<span title="Freestanding Library: inout expected span">[P2833R1]</span> Freestanding Library: inout expected span" to Library Working Group for C++26.</span></a>
      <li><a href="#poll-8-send-p2836r1-stdbasic_const_iterator-should-follow-its-underlying-types-convertibility-to-library-working-group-for-c26-and-as-a-dr-for-c23"><span class="secno">3.8</span> <span class="content">Poll 8: Send "<span title="std::basic_const_iterator should follow its underlying type&apos;s convertibility">[P2836R1]</span> <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>basic_const_iterator</c-></code> should follow its underlying type’s convertibility" to Library Working Group for C++26 and as a DR for C++23.</span></a>
      <li><a href="#poll-9-send-p2868r1-remove-deprecated-stdallocator-typedef-from-c26-to-library-working-group-for-c26"><span class="secno">3.9</span> <span class="content">Poll 9: Send "<span title="Remove Deprecated `std::allocator` Typedef From C++26">[P2868R1]</span> Remove Deprecated <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>allocator</c-></code> Typedef From C++26" to Library Working Group for C++26.</span></a>
      <li><a href="#poll-10-send-p2870r1-remove-basic_stringreserve-from-c26-to-library-working-group-for-c26"><span class="secno">3.10</span> <span class="content">Poll 10: Send "<span title="Remove `basic_string::reserve()` From C++26">[P2870R1]</span> Remove <code class="highlight"><c- n>basic_string</c-><c- o>::</c-><c- n>reserve</c-><c- p>()</c-></code> From C++26" to Library Working Group for C++26.</span></a>
      <li><a href="#poll-11-send-p2871r2-remove-deprecated-unicode-conversion-facets-from-c26-to-library-working-group-for-c2"><span class="secno">3.11</span> <span class="content">Poll 11: Send "<span title="Remove Deprecated Unicode Conversion Facets From C++26">[P2871R2]</span> Remove Deprecated Unicode Conversion Facets From C++26" to Library Working Group for C++2</span></a>
      <li><a href="#poll-12-send-p2905r2-runtime-format-strings-to-library-working-group-for-c26-and-as-a-dr-for-c23"><span class="secno">3.12</span> <span class="content">Poll 12: Send "<span title="Runtime format strings">[P2905R2]</span> Runtime format strings" to Library Working Group for C++26 and as a DR for C++23.</span></a>
      <li><a href="#poll-13-send-p2918r1-runtime-format-strings-ii-to-library-working-group-for-c26"><span class="secno">3.13</span> <span class="content">Poll 13: Send "<span title="Runtime format strings II">[P2918R1]</span> Runtime format strings II" to Library Working Group for C++26.</span></a>
      <li><a href="#poll-14-send-p2937r0-freestanding-remove-strtok-to-library-working-group-for-c26"><span class="secno">3.14</span> <span class="content">Poll 14: Send "<span title="Freestanding: Remove strtok">[P2937R0]</span> Freestanding: Remove <code class="highlight"><c- n>strtok</c-></code>" to Library Working Group for C++26.</span></a>
      <li><a href="#poll-15-send-p2909r2-fix-formatting-of-code-units-as-integers-dude-wheres-my-char-to-library-working-group-for-c26-and-as-a-dr-for-c23"><span class="secno">3.15</span> <span class="content">Poll 15: Send "<span title="Fix formatting of code units as integers (Dude, where&apos;s my char?)">[P2909R2]</span> Fix formatting of code units as integers (Dude, where’s my char?)" to Library Working Group for C++26 and as a DR for C++23.</span></a>
     </ol>
    <li>
     <a href="#references"><span class="secno"></span> <span class="content">References</span></a>
     <ol class="toc">
      <li><a href="#informative"><span class="secno"></span> <span class="content">Informative References</span></a>
     </ol>
   </ol>
  </nav>
  <main>
   <h2 class="heading settled" data-level="1" id="introduction"><span class="secno">1. </span><span class="content">Introduction</span><a class="self-link" href="#introduction"></a></h2>
   <p>In 2023-09, the C++ Library Evolution group conducted a series of electronic decision polls <a data-link-type="biblio" href="https://wg21.link/p2972r0" title="2023-09 Library Evolution Polls">[P2972R0]</a>.
This paper provides the results of those polls and summarizes the results.</p>
   <p>In total, 25 people participated in the polls.
Some participants opted to not vote on some polls (Poll 2, Poll 8, Poll 12, Poll 13, had a low participation rate).
Thank you to everyone who participated, and to the proposal authors for all their hard work!</p>
   <h2 class="heading settled" data-level="2" id="poll-outcomes"><span class="secno">2. </span><span class="content">Poll Outcomes</span><a class="self-link" href="#poll-outcomes"></a></h2>
   <ul>
    <li data-md>
     <p>SF: Strongly Favor.</p>
    <li data-md>
     <p>WF: Weakly Favor.</p>
    <li data-md>
     <p>N: Neutral.</p>
    <li data-md>
     <p>WA: Weakly Against.</p>
    <li data-md>
     <p>SA: Strongly Against.</p>
   </ul>
   <table>
    <tbody>
     <tr>
      <th>Poll 
      <th>SF 
      <th>WF 
      <th>N 
      <th>WA 
      <th>SA 
      <th>Outcome 
     <tr>
      <td> Poll 1: Send "<a data-link-type="biblio" href="https://wg21.link/p0843r9" title="inplace_vector">[P0843R9]</a> <code class="highlight"><c- n>inplace_vector</c-></code>" to Library Working Group for C++26. 
      <td>12 
      <td>6 
      <td>2 
      <td>1 
      <td>1 
      <td>Consensus in favor. 
     <tr>
      <td> Poll 2: Send "<a data-link-type="biblio" href="https://wg21.link/p1068r9" title="Vector API for random number generation">[P1068R9]</a> Vector API for random number generation" to Library Working Group for C++26. 
      <td>6 
      <td>7 
      <td>2 
      <td>0 
      <td>0 
      <td>Strong consensus in favor. 
     <tr>
      <td> Poll 3: Send "<a data-link-type="biblio" href="https://wg21.link/p2447r4" title="std::span over an initializer list">[P2447R4]</a> <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>span</c-></code> over an initializer list" to Library Working Group for C++26. 
      <td>7 
      <td>12 
      <td>0 
      <td>1 
      <td>1 
      <td>Consensus in favor. 
     <tr>
      <td> Poll 4: Send "<a data-link-type="biblio" href="https://wg21.link/p2591r4" title="Concatenation of strings and string views">[P2591R4]</a> Concatenation of strings and string views" to Library Working Group for C++26. 
      <td>8 
      <td>11 
      <td>2 
      <td>1 
      <td>0 
      <td>Strong consensus in favor. 
     <tr>
      <td> Poll 5: Send "<a data-link-type="biblio" href="https://wg21.link/p2819r1" title="Add tuple protocol to complex">[P2819R1]</a> Add tuple protocol to complex" to Library Working Group for C++26. 
      <td>14 
      <td>5 
      <td>1 
      <td>0 
      <td>0 
      <td>Strong consensus in favor. 
     <tr>
      <td> Poll 6: Send "<a data-link-type="biblio" href="https://wg21.link/p2821r4" title="span.at()">[P2821R4]</a> <code class="highlight"><c- n>span</c-><c- p>.</c-><c- n>at</c-><c- p>()</c-></code>" to Library Working Group for C++26. 
      <td>9 
      <td>9 
      <td>2 
      <td>0 
      <td>2 
      <td>Consensus in favor. 
     <tr>
      <td> Poll 7: Send "<a data-link-type="biblio" href="https://wg21.link/p2833r1" title="Freestanding Library: inout expected span">[P2833R1]</a> Freestanding Library: inout expected span" to Library Working Group for C++26. 
      <td>9 
      <td>8 
      <td>0 
      <td>0 
      <td>1 
      <td>Consensus in favor. 
     <tr>
      <td> Poll 8: Send "<a data-link-type="biblio" href="https://wg21.link/p2836r1" title="std::basic_const_iterator should follow its underlying type&apos;s convertibility">[P2836R1]</a> <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>basic_const_iterator</c-></code> should follow its underlying type’s convertibility" to Library Working Group for C++26 and as a DR for C++23. 
      <td>11 
      <td>4 
      <td>0 
      <td>0 
      <td>0 
      <td>Strong consensus in favor. 
     <tr>
      <td> Poll 9: Send "<a data-link-type="biblio" href="https://wg21.link/p2868r1" title="Remove Deprecated `std::allocator` Typedef From C++26">[P2868R1]</a> Remove Deprecated <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>allocator</c-></code> Typedef From C++26" to Library Working Group for C++26. 
      <td>15 
      <td>5 
      <td>1 
      <td>0 
      <td>0 
      <td>Strong consensus in favor. 
     <tr>
      <td> Poll 10: Send "<a data-link-type="biblio" href="https://wg21.link/p2870r1" title="Remove `basic_string::reserve()` From C++26">[P2870R1]</a> Remove <code class="highlight"><c- n>basic_string</c-><c- o>::</c-><c- n>reserve</c-><c- p>()</c-></code> From C++26" to Library Working Group for C++26. 
      <td>16 
      <td>3 
      <td>1 
      <td>1 
      <td>0 
      <td>Strong consensus in favor. 
     <tr>
      <td> Poll 11: Send "<a data-link-type="biblio" href="https://wg21.link/p2871r2" title="Remove Deprecated Unicode Conversion Facets From C++26">[P2871R2]</a> Remove Deprecated Unicode Conversion Facets From C++26" to Library Working Group for C++26. 
      <td>13 
      <td>5 
      <td>1 
      <td>0 
      <td>0 
      <td>Strong consensus in favor. 
     <tr>
      <td> Poll 12: Send "<a data-link-type="biblio" href="https://wg21.link/p2905r2" title="Runtime format strings">[P2905R2]</a> Runtime format strings" to Library Working Group for C++26 and as a DR for C++23. 
      <td>8 
      <td>8 
      <td>0 
      <td>0 
      <td>0 
      <td>Strong consensus in favor. 
     <tr>
      <td> Poll 13: Send "<a data-link-type="biblio" href="https://wg21.link/p2918r1" title="Runtime format strings II">[P2918R1]</a> Runtime format strings II" to Library Working Group for C++26. 
      <td>10 
      <td>4 
      <td>0 
      <td>2 
      <td>0 
      <td>Consensus in favor. 
     <tr>
      <td> Poll 14: Send "<a data-link-type="biblio" href="https://wg21.link/p2937r0" title="Freestanding: Remove strtok">[P2937R0]</a> Freestanding: Remove <code class="highlight"><c- n>strtok</c-></code>" to Library Working Group for C++26. 
      <td>14 
      <td>4 
      <td>1 
      <td>0 
      <td>1 
      <td>Consensus in favor. 
     <tr>
      <td> Poll 15: Send "<a data-link-type="biblio" href="https://wg21.link/p2909r2" title="Fix formatting of code units as integers (Dude, where&apos;s my char?)">[P2909R2]</a> Fix formatting of code units as integers (Dude, where’s my char?)" to Library Working Group for C++26 and as a DR for C++23. 
      <td>10 
      <td>8 
      <td>1 
      <td>0 
      <td>0 
      <td>Strong consensus in favor. 
   </table>
   <p>All the polls have consensus in favor, and will be forwarded to LWG.</p>
   <h2 class="heading settled" data-level="3" id="poll-comments"><span class="secno">3. </span><span class="content">Selected Poll Comments</span><a class="self-link" href="#poll-comments"></a></h2>
   <p>For some of the comments, small parts were removed to anonymize.</p>
   <h3 class="heading settled" data-level="3.1" id="poll-1-send-p0843r9-inplace_vector-to-library-working-group-for-c26"><span class="secno">3.1. </span><span class="content">Poll 1: Send "<a data-link-type="biblio" href="https://wg21.link/p0843r9" title="inplace_vector">[P0843R9]</a> <code class="highlight"><c- n>inplace_vector</c-></code>" to Library Working Group for C++26.</span><a class="self-link" href="#poll-1-send-p0843r9-inplace_vector-to-library-working-group-for-c26"></a></h3>
   <blockquote>
    <p>This is a much needed vocabulary type. Now if only clump/small_vector would get in, then we’d have the complete set.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This will be a useful addition although I feel the unsafe unchecked_push_back is insufficiently motivated based on benchmark data I’ve seen.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This will be a useful addition although I feel the unsafe unchecked_push_back is insufficiently motivated based on benchmark data I’ve seen.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>This has some performance wins, and has the potential to add a resizable container to freestanding. I’m not thrilled with the unchecked calls from a security perspective, but they are far better than any of the other alternatives that have a chance to make it through the committee.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Not sure this has had enough time to bake with the current wording. In particular, I believe that the "constexpr" part is currently unimplementable. But, LWG can always send it back if they agree.</p>
    <p>— Neutral</p>
   </blockquote>
   <blockquote>
    <p>I have some concerns regarding the error handling using exceptions, I think this paper requires more discussion</p>
    <p>— Weakly Against</p>
   </blockquote>
   <blockquote>
    <p>There is are very few scenarios in which bad_alloc is useful, one of them is by logging that the system has run out of memory.
This paper nullifies that use cases by using bad_alloc as the exception it choose to throws, despite having nothing to do at all whatsoever with allocations. What is the point of having a complex hierarchy with bases classes and virtual methods if we are not going to use it correctly?
The paper is not motivated, or rather the motivation for this paper ie supporting "environment which can’t allocate" run afoul if its design "everything throws".
In its current form, this is unlikely to be adopted by the game industry, the embedded community and other such constrained scenario.
This type is therefore not fit for purpose.</p>
    <p>— Strongly Against</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.2" id="poll-2-send-p1068r9-vector-api-for-random-number-generation-to-library-working-group-for-c26"><span class="secno">3.2. </span><span class="content">Poll 2: Send "<a data-link-type="biblio" href="https://wg21.link/p1068r9" title="Vector API for random number generation">[P1068R9]</a> Vector API for random number generation" to Library Working Group for C++26.</span><a class="self-link" href="#poll-2-send-p1068r9-vector-api-for-random-number-generation-to-library-working-group-for-c26"></a></h3>
   <blockquote>
    <p>The current one-element-at a-time interface pessimizes for both vectorization and parallelism. The paper’s new interface corrects this, and also updates random number generation for C++ Ranges.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>It allows to make standard RNG faster even without low-level API if the quality of implementation is good. All the comments were address. Let’s ship it!</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>It is unclear to me whether we have implementation experience with exactly what’s being proposed.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I’m not yet convinced this is required by a large group of standard library users</p>
    <p>— Weakly Favour</p>
   </blockquote>
   <blockquote>
    <p>The wording looks dubious.</p>
    <p>— Neutral</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.3" id="poll-3-send-p2447r4-stdspan-over-an-initializer-list-to-library-working-group-for-c26"><span class="secno">3.3. </span><span class="content">Poll 3: Send "<a data-link-type="biblio" href="https://wg21.link/p2447r4" title="std::span over an initializer list">[P2447R4]</a> <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>span</c-></code> over an initializer list" to Library Working Group for C++26.</span><a class="self-link" href="#poll-3-send-p2447r4-stdspan-over-an-initializer-list-to-library-working-group-for-c26"></a></h3>
   <blockquote>
    <p>This is how it should be. Simple and expected behavior. While incomplete due to lack of guaranteed storage duration, this remains a step in the right direction.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>A initializer_list is essentially an immutable view over an fixed-size array. It seems like an oversight, that such a type wouldn’t be compatible with span.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>
     Every time a class is introduced, we should ask if a constructor from initializer_list makes sense or not, because adding them "after the fact" isn’t always possible.
As an argument type, span
     <const t>
       tries to replace a const vector
      <t>, and span should’ve had initializer_list construction from day one.</t>
     </const>
    </p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>
     It would be unfortunate to have to recommend the <code class="idl"><a data-link-type="idl">1,2,3</a></code> syntax.
The "void two(span
     <const U00032 intU0002C>);" example is the most concerning incompatibility, but the general rule of initializer lists having runtime size is probably sufficient to avoid most confusion there.</const>
    </p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Breaking code is a little bit scary.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>This should not be a DR. I read the poll as if it isn’t.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>The proposal does improve ergonomics. I’m a bit troubled by Section 4.2 ("The initializer_list ctor has high precedence"), in that it might discourage use of spans with compile-time sizes.
On the other hand, there is a straightforward work-around.  I wonder if we could solve this issue with a deduction guide that uses is_constant_evaluated() to determine whether calling .size() on the initializer_list results in a constant expression.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Long time in waiting. There is some worry (hence the WF vote) about the cases of broken code, some of them not entirely contrived, but the benefit in both ease of writing and language consistency (and possibly even performance) clearly supersedes that.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>(...) I believe this feature doesn’t bring so much value but on the other hand it introduces the breaking change and enables simpler use-cases like <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>span</c-><c- o>&lt;</c-><c- k>const</c-> <c- b>int</c-><c- o>></c-> <c- n>s</c-><c- p>{</c-><c- mi>1</c-><c- p>,</c-><c- mi>2</c-><c- p>,</c-><c- mi>3</c-><c- p>};</c-></code> which is error prone. Yeah, it’s better than <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>span</c-><c- o>&lt;</c-><c- b>int</c-><c- o>></c-> <c- n>s</c-><c- p>{</c-><c- mi>1</c-><c- p>,</c-><c- mi>2</c-><c- p>,</c-><c- mi>3</c-><c- p>};</c-></code> because of <code class="highlight"><c- k>const</c-></code> and far better than <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>span</c-> <c- n>s</c-><c- p>{</c-><c- mi>1</c-><c- p>,</c-><c- mi>2</c-><c- p>,</c-><c- mi>3</c-><c- p>};</c-></code> and doesn’t work because deduction guides are not enabled for this use-case (fortunately) but still I believe danger for the user is more than the value since the applicability of the API is pretty narrow to me.
On the other hand, we already have precedence in the standard where class initialized with temporary could immediately dangle. That’s why I am weakly against. If this papers lands, so be it.</p>
    <p>— Weakly Against</p>
   </blockquote>
   <blockquote>
    <p>span is not a container and should not pretend to be one.</p>
    <p>— Strongly Against</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.4" id="poll-4-send-p2591r4-concatenation-of-strings-and-string-views-to-library-working-group-for-c26"><span class="secno">3.4. </span><span class="content">Poll 4: Send "<a data-link-type="biblio" href="https://wg21.link/p2591r4" title="Concatenation of strings and string views">[P2591R4]</a> Concatenation of strings and string views" to Library Working Group for C++26.</span><a class="self-link" href="#poll-4-send-p2591r4-concatenation-of-strings-and-string-views-to-library-working-group-for-c26"></a></h3>
   <blockquote>
    <p>I’ve lost track of how many times I had to workaround these missing operators.
While it may have been good intentioned to leave them out until we can come up with a lazy concatenation design, said feature never materialized and most probably shouldn’t be spelled as operator+ to begin with.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This improves ergonomics and teachability.
I am convinced by the arguments in Section 2.1 ("Why are those overloads missing in the first place?") why we should not delay adding this feature in the name of a nonexistent future proposal that could not be implemented fully anyway.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>I strongly believe that we should NOT be updating the __cpp_­lib_­string_­view feature test macro, as we are making NO changes to string_view.
We should add a new feature test macro instead (as none of the string ones look to be appropriate).
(I would have voted SF instead of WF had it been a different feature test macro).
Also, breaking user code is a little bit scary.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Fixes an inconsistency in the library users have been complaining about (https://stackoverflow.com/q/44636549/471164).</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>The proposal is the only reasonable interpretation of the syntax (and its discussion of the history adequately explains the omission as no longer relevant).</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Slightly hesitant due to the conversion-related risks. Overall though this is a highly missed addition, long time due.
With this we will no longer have to guide devs to define string constants as constexpr string_view – but only if they don’t need them to be concatenated, in which case the unfortunate guidance becomes to use const std::string instead.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>It does fix a mistake, but unimportant.</p>
    <p>— Neutral</p>
   </blockquote>
   <blockquote>
    <p>Worried about the issues raised in Annex C;
I’d prefer to see just the string + string_view overloads and not the additional overloads specified by [tab:string.op.plus.string_view.overloads].</p>
    <p>— Weakly Against</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.5" id="poll-5-send-p2819r1-add-tuple-protocol-to-complex-to-library-working-group-for-c26"><span class="secno">3.5. </span><span class="content">Poll 5: Send "<a data-link-type="biblio" href="https://wg21.link/p2819r1" title="Add tuple protocol to complex">[P2819R1]</a> Add tuple protocol to complex" to Library Working Group for C++26.</span><a class="self-link" href="#poll-5-send-p2819r1-add-tuple-protocol-to-complex-to-library-working-group-for-c26"></a></h3>
   <blockquote>
    <p>This is how it should be. Simple and expected behavior. It is expected that new features will be consistent with the rest of the language.
As such this is more a spec fix or completion of previous work.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Good facility for std::complex. Assuming the comment on tuple-like concept is addressed I have no objections to that.
Hopefully, one day we fix the tuple protocol to make it generic enough but it’s a separate story.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>
     There was a concern about using hidden friends (although I’m not sure it was brought up formally):
The main difference between having a normal function vs hidden friend is whether or not it is findable for types that are convertible to complex
     <t>.</t>
    </p>
    <p>
     E.g. given:
struct my_imaginary {
  double scale;
  operator std::complex
     <double>() const noexcept { return {0, scale}; }
};</double>
    </p>
    <p>
     Then the following will only work if std::complex
     <t> has non-hidden get() functions:
my_imaginary x;
auto [r, i] = x;  // error: If get() is a hidden friend.</t>
    </p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>It makes sense for complex to be decomposable but should it be tuple_like?</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Looks acceptable. I can’t get excited about using structured bindings.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Applying get&lt;0>(c) to complex values may spoil redability of mathematically intensive code, but at the same the paper adds better integration with other standard facilities. Thus neutral.</p>
    <p>— Neutral</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.6" id="poll-6-send-p2821r4-spanat-to-library-working-group-for-c26"><span class="secno">3.6. </span><span class="content">Poll 6: Send "<a data-link-type="biblio" href="https://wg21.link/p2821r4" title="span.at()">[P2821R4]</a> <code class="highlight"><c- n>span</c-><c- p>.</c-><c- n>at</c-><c- p>()</c-></code>" to Library Working Group for C++26.</span><a class="self-link" href="#poll-6-send-p2821r4-spanat-to-library-working-group-for-c26"></a></h3>
   <blockquote>
    <p>I’ve already used "span.at()" a few times in code bases, just so that I can be reminded by the compiler that it doesn’t exist yet.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>While it doesn’t bring much value to std::span itself it does bring the value to a generic code and it makes API more consistent.
Since we can now add classes partially to freestanding I don’t have any problems with adding this method.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>We can entertain lengthy discussions about how and why std::span differs from the original gls::span, but at this point we should simply strive for consistency.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>It is embarrassing not to have it. It is safe and consistent. We need more safe functions instead of unsafe ones.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This addition makes span more consistent with vector. I also appreciate that the author has taken the time to address freestanding.
However, I disagree that "a function that throws when the input is out of bounds" is necessarily "safer" than a function with a nontrivial precondition. I’m not an expert in functional safety, but I’ve heard such experts share my opinion.
My concern only addresses this one motivation for the paper; making span consistent with vector justifies the paper in itself.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>So long as we’re happy having classes have incomplete interfaces in freestanding, this is only reasonable based on consistency, since there’s no cost to having the feature.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Not convinced that this is worth adding.</p>
    <p>— Neutral</p>
   </blockquote>
   <blockquote>
    <p>This is extremely poorly motivated in my view.
Throwing exception of developer error is not something we should encourage, and it certainly does not encourage safety.
Consistency with past mistakes is also not a very convincing argument.
Ask your local standard library implementer an harden build that terminates on out-of-bound. These things exist and they are great!</p>
    <p>— Strongly Against</p>
   </blockquote>
   <blockquote>
    <p>This is safety theatre (a term analogous to the well understood term "security theater").
MISRA doesn’t require usage of .at() and I don’t see C++ engineers adopting .at() any time soon.
If we want to reduce C++ vulnerabilities due to memory safety violations, we should attack that problem directly instead of making changes that make us feel good, but do nothing to solve our problems.</p>
    <p>— Strongly Against</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.7" id="poll-7-send-p2833r1-freestanding-library-inout-expected-span-to-library-working-group-for-c26"><span class="secno">3.7. </span><span class="content">Poll 7: Send "<a data-link-type="biblio" href="https://wg21.link/p2833r1" title="Freestanding Library: inout expected span">[P2833R1]</a> Freestanding Library: inout expected span" to Library Working Group for C++26.</span><a class="self-link" href="#poll-7-send-p2833r1-freestanding-library-inout-expected-span-to-library-working-group-for-c26"></a></h3>
   <blockquote>
    <p>freestanding has needed some kind of error handling mechanism for awhile, so this will be a big win.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This will aid span’s adoption which is essential since it is a fundamental type.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Would have been nice to have the freestanding features done in fewer papers to save time for LEWG.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>We don’t use freestanding, but these additions seem reasonable and useful for those that do.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>The addition of these features to the freestanding subset should be non-controversial.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I’m unconvinced that spending time on the freestanding dialect of C++ is in the interest of our users.</p>
    <p>— Strongly Against</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.8" id="poll-8-send-p2836r1-stdbasic_const_iterator-should-follow-its-underlying-types-convertibility-to-library-working-group-for-c26-and-as-a-dr-for-c23"><span class="secno">3.8. </span><span class="content">Poll 8: Send "<a data-link-type="biblio" href="https://wg21.link/p2836r1" title="std::basic_const_iterator should follow its underlying type&apos;s convertibility">[P2836R1]</a> <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>basic_const_iterator</c-></code> should follow its underlying type’s convertibility" to Library Working Group for C++26 and as a DR for C++23.</span><a class="self-link" href="#poll-8-send-p2836r1-stdbasic_const_iterator-should-follow-its-underlying-types-convertibility-to-library-working-group-for-c26-and-as-a-dr-for-c23"></a></h3>
   <blockquote>
    <p>This fixes a deficiency in the current C++ Standard.  I agree that this change should be considered library DR.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>We need to add uniformity, and "wrapper types" should behave as the wrapped type</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>I like not breaking C++20 code</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I’m not a fan of the DR part.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>The proposed conversions could in theory produce undesired complications, but I haven’t checked.</p>
    <p>— I do not want to participate in this poll</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.9" id="poll-9-send-p2868r1-remove-deprecated-stdallocator-typedef-from-c26-to-library-working-group-for-c26"><span class="secno">3.9. </span><span class="content">Poll 9: Send "<a data-link-type="biblio" href="https://wg21.link/p2868r1" title="Remove Deprecated `std::allocator` Typedef From C++26">[P2868R1]</a> Remove Deprecated <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>allocator</c-></code> Typedef From C++26" to Library Working Group for C++26.</span><a class="self-link" href="#poll-9-send-p2868r1-remove-deprecated-stdallocator-typedef-from-c26-to-library-working-group-for-c26"></a></h3>
   <blockquote>
    <p>Once a good idea, but now std::allocator is no longer necessary.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Although implementations will likely leave these in, the purpose of deprecation is ultimately to remove things, and so this should be done.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>We must remove or control baggage if C++ is to grow, change and remain relevant.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>I’ll finger the elephant in the room: DRY violation. This is an attribute, so its single source of truth should be allocator_traits, it has no business getting itself duplicated anywhere else.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>We have experience with the removed members in std::allocator.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.10" id="poll-10-send-p2870r1-remove-basic_stringreserve-from-c26-to-library-working-group-for-c26"><span class="secno">3.10. </span><span class="content">Poll 10: Send "<a data-link-type="biblio" href="https://wg21.link/p2870r1" title="Remove `basic_string::reserve()` From C++26">[P2870R1]</a> Remove <code class="highlight"><c- n>basic_string</c-><c- o>::</c-><c- n>reserve</c-><c- p>()</c-></code> From C++26" to Library Working Group for C++26.</span><a class="self-link" href="#poll-10-send-p2870r1-remove-basic_stringreserve-from-c26-to-library-working-group-for-c26"></a></h3>
   <blockquote>
    <p>I’m not sure why this function even exists in the first place. The default parameter that was originally supplied looks like a design bug - especially as it was exclusive to basic_string.
Given that we have a replacement since C++11 and it isn’t even functional anymore since C++20 I see no reason to retain this overload.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Although implementations will likely leave these in, the purpose of deprecation is ultimately to remove things, and so this should be done.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>We must remove or control baggage if C++ is to grow, change and remain relevant.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>The real semantic change (which is justifiable) has already occurred.  This is, if anything, helpfully alerting people to the fact.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I’m worried about the reported lack of deprecation warnings, and about the paper missing any research into the amount of existing code which may be broken by this.
I think straight up removal may surprise some users by providing them no immediate clue as to how to modify their code.
Therefore the path forward should be one cycle in which this function is implemented via a static_assert(false) with a relevant error message, followed by complete removal only in the next cycle (C++29).</p>
    <p>— Weakly Against</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.11" id="poll-11-send-p2871r2-remove-deprecated-unicode-conversion-facets-from-c26-to-library-working-group-for-c2"><span class="secno">3.11. </span><span class="content">Poll 11: Send "<a data-link-type="biblio" href="https://wg21.link/p2871r2" title="Remove Deprecated Unicode Conversion Facets From C++26">[P2871R2]</a> Remove Deprecated Unicode Conversion Facets From C++26" to Library Working Group for C++2</span><a class="self-link" href="#poll-11-send-p2871r2-remove-deprecated-unicode-conversion-facets-from-c26-to-library-working-group-for-c2"></a></h3>
   <blockquote>
    <p>Having these seems worse than having nothing.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>The implementation is broken in MSVC at one point anyway.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Regularly removing deprecated functionality is a good practice.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This feature has never fundamentally worked correctly.  Deprecation and, now, removal even without replacement is appropriate.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Due to lack of usage experience I can’t comment on these facets.</p>
    <p>— Neutral</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.12" id="poll-12-send-p2905r2-runtime-format-strings-to-library-working-group-for-c26-and-as-a-dr-for-c23"><span class="secno">3.12. </span><span class="content">Poll 12: Send "<a data-link-type="biblio" href="https://wg21.link/p2905r2" title="Runtime format strings">[P2905R2]</a> Runtime format strings" to Library Working Group for C++26 and as a DR for C++23.</span><a class="self-link" href="#poll-12-send-p2905r2-runtime-format-strings-to-library-working-group-for-c26-and-as-a-dr-for-c23"></a></h3>
   <blockquote>
    <p>This is the right thing to do.  We should also make this a DR for C++23.  I can’t think of any correct code that would be broken by doing so.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Improves safety of a formatting API by preventing some lifetime issues.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>I’m not a fan of the DR part, but it seems more plausible here than in some other cases.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Preventing dangling is great but it is concerning that we continue to retroactively modify std::format two standard cycles after the feature was initially added.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Obviously being able to use such strings is valuable, but the change could easily be unfortunately invasive; I haven’t tried to vet it independently.</p>
    <p>— I do not want to participate in this poll</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.13" id="poll-13-send-p2918r1-runtime-format-strings-ii-to-library-working-group-for-c26"><span class="secno">3.13. </span><span class="content">Poll 13: Send "<a data-link-type="biblio" href="https://wg21.link/p2918r1" title="Runtime format strings II">[P2918R1]</a> Runtime format strings II" to Library Working Group for C++26.</span><a class="self-link" href="#poll-13-send-p2918r1-runtime-format-strings-ii-to-library-working-group-for-c26"></a></h3>
   <blockquote>
    <p>This is a good idea. Separating this from P2905 (the safety fix alone) was also a good idea, so that P2905 could be made a DR, while P2918 can be introduced "normally" in C++26.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>A straight-forward extension to std::format that doesn’t require changing existing standards and enables to-date missing functionality.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>A very important addition to std::format that allows to explicitly opt out of compile-time checks instead of misusing type erased APIs.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Has implementation and usage experience.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>The new API seems a bit confusing, but not enough to preclude the important functionality.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Users expect to be able to use a std::string as the first argument of std::format.
If we lack the language facilities to provide this, we should add them instead of spending time with unsatisfying workarounds.</p>
    <p>— Weakly Against</p>
   </blockquote>
   <blockquote>
    <p>Why not std::runtime_format(str, 42)</p>
    <p>— Weakly Against</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.14" id="poll-14-send-p2937r0-freestanding-remove-strtok-to-library-working-group-for-c26"><span class="secno">3.14. </span><span class="content">Poll 14: Send "<a data-link-type="biblio" href="https://wg21.link/p2937r0" title="Freestanding: Remove strtok">[P2937R0]</a> Freestanding: Remove <code class="highlight"><c- n>strtok</c-></code>" to Library Working Group for C++26.</span><a class="self-link" href="#poll-14-send-p2937r0-freestanding-remove-strtok-to-library-working-group-for-c26"></a></h3>
   <blockquote>
    <p>One foot-gun less ... strtok should actually be removed from the entire standard library.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This function should not only be removed from freestanding, it should be yanked from the standard library as a whole.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Keep C++ freestanding in line with C freestanding.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>One could argue that strtok on freestanding should just not be thread-safe at all, but the fact that C doesn’t expect it to be there tips the balance in favor of removing it. (Who uses it anyway?)</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Would have been nice to have the freestanding features done in fewer papers to save time for LEWG</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I’m unconvinced that spending time on the freestanding dialect of C++ is in the interest of our users.</p>
    <p>— Strongly Against</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.15" id="poll-15-send-p2909r2-fix-formatting-of-code-units-as-integers-dude-wheres-my-char-to-library-working-group-for-c26-and-as-a-dr-for-c23"><span class="secno">3.15. </span><span class="content">Poll 15: Send "<a data-link-type="biblio" href="https://wg21.link/p2909r2" title="Fix formatting of code units as integers (Dude, where&apos;s my char?)">[P2909R2]</a> Fix formatting of code units as integers (Dude, where’s my char?)" to Library Working Group for C++26 and as a DR for C++23.</span><a class="self-link" href="#poll-15-send-p2909r2-fix-formatting-of-code-units-as-integers-dude-wheres-my-char-to-library-working-group-for-c26-and-as-a-dr-for-c23"></a></h3>
   <blockquote>
    <p>This feels like the right thing to do, even if it is a breaking change.  It’s important for Standard Library output to be consistent.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Spec fixes should be done, especially when there is negligible breakage.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Fixes a problematic behavior in formatting characters as integers and makes formatting consistent among platforms.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Improved consistency is great but we are yet again retroactively changing the meaning of std::format.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>No one expects code units to actually be negative and relies on two’s complement (and little real arithmetic) to make that never matter in practice.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Runtime change in behavior of C++20 facilities makes me really nervous, even when the change in an improvement.</p>
    <p>— Neutral</p>
   </blockquote>
  </main>
<script>
(function() {
  "use strict";
  var collapseSidebarText = '<span aria-hidden="true">←</span> '
                          + '<span>Collapse Sidebar</span>';
  var expandSidebarText   = '<span aria-hidden="true">→</span> '
                          + '<span>Pop Out Sidebar</span>';
  var tocJumpText         = '<span aria-hidden="true">↑</span> '
                          + '<span>Jump to Table of Contents</span>';

  var sidebarMedia = window.matchMedia('screen and (min-width: 78em)');
  var autoToggle   = function(e){ toggleSidebar(e.matches) };
  if(sidebarMedia.addListener) {
    sidebarMedia.addListener(autoToggle);
  }

  function toggleSidebar(on) {
    if (on == undefined) {
      on = !document.body.classList.contains('toc-sidebar');
    }

    /* Don’t scroll to compensate for the ToC if we’re above it already. */
    var headY = 0;
    var head = document.querySelector('.head');
    if (head) {
      // terrible approx of "top of ToC"
      headY += head.offsetTop + head.offsetHeight;
    }
    var skipScroll = window.scrollY < headY;

    var toggle = document.getElementById('toc-toggle');
    var tocNav = document.getElementById('toc');
    if (on) {
      var tocHeight = tocNav.offsetHeight;
      document.body.classList.add('toc-sidebar');
      document.body.classList.remove('toc-inline');
      toggle.innerHTML = collapseSidebarText;
      if (!skipScroll) {
        window.scrollBy(0, 0 - tocHeight);
      }
      tocNav.focus();
      sidebarMedia.addListener(autoToggle); // auto-collapse when out of room
    }
    else {
      document.body.classList.add('toc-inline');
      document.body.classList.remove('toc-sidebar');
      toggle.innerHTML = expandSidebarText;
      if (!skipScroll) {
        window.scrollBy(0, tocNav.offsetHeight);
      }
      if (toggle.matches(':hover')) {
        /* Unfocus button when not using keyboard navigation,
           because I don’t know where else to send the focus. */
        toggle.blur();
      }
    }
  }

  function createSidebarToggle() {
    /* Create the sidebar toggle in JS; it shouldn’t exist when JS is off. */
    var toggle = document.createElement('a');
      /* This should probably be a button, but appearance isn’t standards-track.*/
    toggle.id = 'toc-toggle';
    toggle.class = 'toc-toggle';
    toggle.href = '#toc';
    toggle.innerHTML = collapseSidebarText;

    sidebarMedia.addListener(autoToggle);
    var toggler = function(e) {
      e.preventDefault();
      sidebarMedia.removeListener(autoToggle); // persist explicit off states
      toggleSidebar();
      return false;
    }
    toggle.addEventListener('click', toggler, false);


    /* Get <nav id=toc-nav>, or make it if we don’t have one. */
    var tocNav = document.getElementById('toc-nav');
    if (!tocNav) {
      tocNav = document.createElement('p');
      tocNav.id = 'toc-nav';
      /* Prepend for better keyboard navigation */
      document.body.insertBefore(tocNav, document.body.firstChild);
    }
    /* While we’re at it, make sure we have a Jump to Toc link. */
    var tocJump = document.getElementById('toc-jump');
    if (!tocJump) {
      tocJump = document.createElement('a');
      tocJump.id = 'toc-jump';
      tocJump.href = '#toc';
      tocJump.innerHTML = tocJumpText;
      tocNav.appendChild(tocJump);
    }

    tocNav.appendChild(toggle);
  }

  var toc = document.getElementById('toc');
  if (toc) {
    createSidebarToggle();
    toggleSidebar(sidebarMedia.matches);

    /* If the sidebar has been manually opened and is currently overlaying the text
       (window too small for the MQ to add the margin to body),
       then auto-close the sidebar once you click on something in there. */
    toc.addEventListener('click', function(e) {
      if(e.target.tagName.toLowerCase() == "a" && document.body.classList.contains('toc-sidebar') && !sidebarMedia.matches) {
        toggleSidebar(false);
      }
    }, false);
  }
  else {
    console.warn("Can’t find Table of Contents. Please use <nav id='toc'> around the ToC.");
  }

  /* Wrap tables in case they overflow */
  var tables = document.querySelectorAll(':not(.overlarge) > table.data, :not(.overlarge) > table.index');
  var numTables = tables.length;
  for (var i = 0; i < numTables; i++) {
    var table = tables[i];
    var wrapper = document.createElement('div');
    wrapper.className = 'overlarge';
    table.parentNode.insertBefore(wrapper, table);
    wrapper.appendChild(table);
  }

})();
</script>
  <h2 class="no-num no-ref heading settled" id="references"><span class="content">References</span><a class="self-link" href="#references"></a></h2>
  <h3 class="no-num no-ref heading settled" id="informative"><span class="content">Informative References</span><a class="self-link" href="#informative"></a></h3>
  <dl>
   <dt id="biblio-p0843r9">[P0843R9]
   <dd>Gonzalo Brito Gadeschi, Timur Doumler, Nevin Liber, David Sankel. <a href="https://wg21.link/p0843r9"><cite>inplace_vector</cite></a>. 14 September 2023. URL: <a href="https://wg21.link/p0843r9">https://wg21.link/p0843r9</a>
   <dt id="biblio-p1068r9">[P1068R9]
   <dd>Ilya Burylov, Pavel Dyakov, Ruslan Arutyunyan, Andrey Nikolaev, Alina Elizarova. <a href="https://wg21.link/p1068r9"><cite>Vector API for random number generation</cite></a>. 14 September 2023. URL: <a href="https://wg21.link/p1068r9">https://wg21.link/p1068r9</a>
   <dt id="biblio-p2447r4">[P2447R4]
   <dd>Arthur O'Dwyer, Federico Kircheis. <a href="https://wg21.link/p2447r4"><cite>std::span over an initializer list</cite></a>. 14 May 2023. URL: <a href="https://wg21.link/p2447r4">https://wg21.link/p2447r4</a>
   <dt id="biblio-p2591r4">[P2591R4]
   <dd>Giuseppe D'Angelo. <a href="https://wg21.link/p2591r4"><cite>Concatenation of strings and string views</cite></a>. 11 July 2023. URL: <a href="https://wg21.link/p2591r4">https://wg21.link/p2591r4</a>
   <dt id="biblio-p2819r1">[P2819R1]
   <dd>Michael Florian Hava, Christoph Hofer. <a href="https://wg21.link/p2819r1"><cite>Add tuple protocol to complex</cite></a>. 14 July 2023. URL: <a href="https://wg21.link/p2819r1">https://wg21.link/p2819r1</a>
   <dt id="biblio-p2821r4">[P2821R4]
   <dd>Jarrad J. Waterloo. <a href="https://wg21.link/p2821r4"><cite>span.at()</cite></a>. 26 July 2023. URL: <a href="https://wg21.link/p2821r4">https://wg21.link/p2821r4</a>
   <dt id="biblio-p2833r1">[P2833R1]
   <dd>Ben Craig. <a href="https://wg21.link/p2833r1"><cite>Freestanding Library: inout expected span</cite></a>. 19 August 2023. URL: <a href="https://wg21.link/p2833r1">https://wg21.link/p2833r1</a>
   <dt id="biblio-p2836r1">[P2836R1]
   <dd>Christopher Di Bella. <a href="https://wg21.link/p2836r1"><cite>std::basic_const_iterator should follow its underlying type's convertibility</cite></a>. 11 July 2023. URL: <a href="https://wg21.link/p2836r1">https://wg21.link/p2836r1</a>
   <dt id="biblio-p2868r1">[P2868R1]
   <dd>Alisdair Meredith. <a href="https://wg21.link/p2868r1"><cite>Remove Deprecated `std::allocator` Typedef From C++26</cite></a>. 15 August 2023. URL: <a href="https://wg21.link/p2868r1">https://wg21.link/p2868r1</a>
   <dt id="biblio-p2870r1">[P2870R1]
   <dd>Alisdair Meredith. <a href="https://wg21.link/p2870r1"><cite>Remove `basic_string::reserve()` From C++26</cite></a>. 16 August 2023. URL: <a href="https://wg21.link/p2870r1">https://wg21.link/p2870r1</a>
   <dt id="biblio-p2871r2">[P2871R2]
   <dd>Alisdair Meredith. <a href="https://wg21.link/p2871r2"><cite>Remove Deprecated Unicode Conversion Facets From C++26</cite></a>. 15 September 2023. URL: <a href="https://wg21.link/p2871r2">https://wg21.link/p2871r2</a>
   <dt id="biblio-p2905r2">[P2905R2]
   <dd>Victor Zverovich. <a href="https://wg21.link/p2905r2"><cite>Runtime format strings</cite></a>. 23 July 2023. URL: <a href="https://wg21.link/p2905r2">https://wg21.link/p2905r2</a>
   <dt id="biblio-p2909r2">[P2909R2]
   <dd>Victor Zverovich. <a href="https://wg21.link/p2909r2"><cite>Fix formatting of code units as integers (Dude, where's my char?)</cite></a>. 16 September 2023. URL: <a href="https://wg21.link/p2909r2">https://wg21.link/p2909r2</a>
   <dt id="biblio-p2918r1">[P2918R1]
   <dd>Victor Zverovich. <a href="https://wg21.link/p2918r1"><cite>Runtime format strings II</cite></a>. 15 July 2023. URL: <a href="https://wg21.link/p2918r1">https://wg21.link/p2918r1</a>
   <dt id="biblio-p2937r0">[P2937R0]
   <dd>Ben Craig. <a href="https://wg21.link/p2937r0"><cite>Freestanding: Remove strtok</cite></a>. 2 July 2023. URL: <a href="https://wg21.link/p2937r0">https://wg21.link/p2937r0</a>
   <dt id="biblio-p2972r0">[P2972R0]
   <dd>Inbal Levi, Ben Craig, Fabio Fracassi, Corentin Jabot, Nevin Liber, Billy Baker. <a href="https://wg21.link/p2972r0"><cite>2023-09 Library Evolution Polls</cite></a>. 18 September 2023. URL: <a href="https://wg21.link/p2972r0">https://wg21.link/p2972r0</a>
  </dl>