<!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>P2575R0: 2022-05 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;
		}
		#toc .content:hover,
		#toc .content:focus {
			background: rgba(75%, 75%, 75%, .25);
			background: var(--a-hover-bg);
			border-bottom: 3px solid #054572;
			border-bottom: 3px solid var(--toclink-underline);
			margin-bottom: -3px;
		}
		#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 1f1661843, updated Wed Dec 15 11:50:57 2021 -0800" name="generator">
  <link href="https://wg21.link/P2575" rel="canonical">
  <link href="https://isocpp.org/favicon.ico" rel="icon">
  <meta content="5a6693af433007294e2b69070e1e12ab30762e8f" name="document-revision">
<style>
table, th, tr, td {
  border: 2px solid black !important;
}
@media (prefers-color-scheme: dark) {
  table, th, tr, td {
    border: 2px solid white !important;
  }
}
</style>
<style>/* 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;
}</style>
<style>/* 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;
}</style>
<style>/* 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>/* style-issues */

a[href].issue-return {
    float: right;
    float: inline-end;
    color: var(--issueheading-text);
    font-weight: bold;
    text-decoration: none;
}
</style>
<style>/* 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>/* 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%;
}
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>
<style>/* style-darkmode */

@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; }
}
@media (prefers-color-scheme: dark) {
    :root {
        --selflink-text: black;
        --selflink-bg: silver;
        --selflink-hover-text: white;
    }
}

@media (prefers-color-scheme: dark) {
    .highlight:not(.idl) { background: rgba(255, 255, 255, .05); }

    c-[a] { color: #d33682 } /* Keyword.Declaration */
    c-[b] { color: #d33682 } /* Keyword.Type */
    c-[c] { color: #2aa198 } /* Comment */
    c-[d] { color: #2aa198 } /* Comment.Multiline */
    c-[e] { color: #268bd2 } /* Name.Attribute */
    c-[f] { color: #b58900 } /* Name.Tag */
    c-[g] { color: #cb4b16 } /* Name.Variable */
    c-[k] { color: #d33682 } /* Keyword */
    c-[l] { color: #657b83 } /* Literal */
    c-[m] { color: #657b83 } /* Literal.Number */
    c-[n] { color: #268bd2 } /* Name */
    c-[o] { color: #657b83 } /* Operator */
    c-[p] { color: #657b83 } /* Punctuation */
    c-[s] { color: #6c71c4 } /* Literal.String */
    c-[t] { color: #6c71c4 } /* Literal.String.Single */
    c-[u] { color: #6c71c4 } /* Literal.String.Double */
    c-[ch] { color: #2aa198 } /* Comment.Hashbang */
    c-[cp] { color: #2aa198 } /* Comment.Preproc */
    c-[cpf] { color: #2aa198 } /* Comment.PreprocFile */
    c-[c1] { color: #2aa198 } /* Comment.Single */
    c-[cs] { color: #2aa198 } /* Comment.Special */
    c-[kc] { color: #d33682 } /* Keyword.Constant */
    c-[kn] { color: #d33682 } /* Keyword.Namespace */
    c-[kp] { color: #d33682 } /* Keyword.Pseudo */
    c-[kr] { color: #d33682 } /* Keyword.Reserved */
    c-[ld] { color: #657b83 } /* Literal.Date */
    c-[nc] { color: #268bd2 } /* Name.Class */
    c-[no] { color: #268bd2 } /* Name.Constant */
    c-[nd] { color: #268bd2 } /* Name.Decorator */
    c-[ni] { color: #268bd2 } /* Name.Entity */
    c-[ne] { color: #268bd2 } /* Name.Exception */
    c-[nf] { color: #268bd2 } /* Name.Function */
    c-[nl] { color: #268bd2 } /* Name.Label */
    c-[nn] { color: #268bd2 } /* Name.Namespace */
    c-[py] { color: #268bd2 } /* Name.Property */
    c-[ow] { color: #657b83 } /* Operator.Word */
    c-[mb] { color: #657b83 } /* Literal.Number.Bin */
    c-[mf] { color: #657b83 } /* Literal.Number.Float */
    c-[mh] { color: #657b83 } /* Literal.Number.Hex */
    c-[mi] { color: #657b83 } /* Literal.Number.Integer */
    c-[mo] { color: #657b83 } /* Literal.Number.Oct */
    c-[sa] { color: #6c71c4 } /* Literal.String.Affix */
    c-[sb] { color: #6c71c4 } /* Literal.String.Backtick */
    c-[sc] { color: #6c71c4 } /* Literal.String.Char */
    c-[dl] { color: #6c71c4 } /* Literal.String.Delimiter */
    c-[sd] { color: #6c71c4 } /* Literal.String.Doc */
    c-[se] { color: #6c71c4 } /* Literal.String.Escape */
    c-[sh] { color: #6c71c4 } /* Literal.String.Heredoc */
    c-[si] { color: #6c71c4 } /* Literal.String.Interpol */
    c-[sx] { color: #6c71c4 } /* Literal.String.Other */
    c-[sr] { color: #6c71c4 } /* Literal.String.Regex */
    c-[ss] { color: #6c71c4 } /* Literal.String.Symbol */
    c-[fm] { color: #268bd2 } /* Name.Function.Magic */
    c-[vc] { color: #cb4b16 } /* Name.Variable.Class */
    c-[vg] { color: #cb4b16 } /* Name.Variable.Global */
    c-[vi] { color: #cb4b16 } /* Name.Variable.Instance */
    c-[vm] { color: #cb4b16 } /* Name.Variable.Magic */
    c-[il] { color: #657b83 } /* Literal.Number.Integer.Long */
}
</style>
 <body class="h-entry">
  <div class="head">
   <p data-fill-with="logo"></p>
   <h1 class="p-name no-ref" id="title">P2575R0<br>2022-05 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="2022-06-22">2022-06-22</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:brycelelbach@gmail.com">Bryce Adelstein Lelbach (he/him/his) — Library Evolution 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:f.fracassi@gmx.net">Fabio Fracassi — Library Evolution Vice 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 Vice Chair</a> (<span class="p-org org">NI</span>)
     <dd class="editor p-author h-card vcard"><a class="p-name fn u-email email" href="mailto:sinbal2l@gmail.com">Inbal Levi — Ranges Chair (SG9) and Library Mailing List Review Manager</a>
     <dt>Source:
     <dd><a href="https://github.com/brycelelbach/wg21_p2575_2022_05_library_evolution_poll_outcomes/blob/main/2022_05_library_evolution_poll_outcomes.bs">GitHub</a>
     <dt>Issue Tracking:
     <dd><a href="https://github.com/brycelelbach/wg21_p2575_2022_05_library_evolution_poll_outcomes/issues">GitHub</a>
     <dt>Project:
     <dd>ISO/IEC JTC1/SC22/WG21 14882: Programming Language — C++
     <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="#selected-poll-comments"><span class="secno">3</span> <span class="content">Selected Poll Comments</span></a>
     <ol class="toc">
      <li>
       <a href="#polls-cpp23"><span class="secno">3.1</span> <span class="content">C++23 Polls</span></a>
       <ol class="toc">
        <li><a href="#p1885r10-naming-text-encodings-to-demystify-them"><span class="secno">3.1.1</span> <span class="content"><span>[P1885R10]</span> Naming Text Encodings to Demystify Them</span></a>
        <li><a href="#p0792r8-function_ref"><span class="secno">3.1.2</span> <span class="content"><span>[P0792R8]</span> <code class="highlight"><c- n>function_ref</c-></code></span></a>
        <li><a href="#p1223r3-find_last"><span class="secno">3.1.3</span> <span class="content"><span>[P1223R3]</span> <code class="highlight"><c- n>find_last</c-></code></span></a>
        <li><a href="#p1169r3-static-operator"><span class="secno">3.1.4</span> <span class="content"><span>[P1169R3]</span> Static <code class="highlight"><c- k>operator</c-><c- p>()</c-></code></span></a>
        <li><a href="#p2553r1-make-mdspan-size_type-controllable"><span class="secno">3.1.5</span> <span class="content"><span>[P2553R1]</span> Make <code class="highlight"><c- n>mdspan</c-></code> <code class="highlight"><c- n>size_type</c-></code> Controllable</span></a>
        <li><a href="#p2554r0-c-array-interoperability-of-mdspan"><span class="secno">3.1.6</span> <span class="content"><span>[P2554R0]</span> C-Array Interoperability Of <code class="highlight"><c- n>mdspan</c-></code></span></a>
        <li><a href="#p2540r0-empty-product-for-certain-views"><span class="secno">3.1.7</span> <span class="content"><span>[P2540R0]</span> Empty Product For Certain Views</span></a>
        <li><a href="#p2538r0-adl-proof-projected"><span class="secno">3.1.8</span> <span class="content"><span>[P2538R0]</span> ADL-Proof <code class="highlight"><c- n>projected</c-></code></span></a>
        <li><a href="#lwg3646-rangesview_interfacesize-returns-a-signed-type"><span class="secno">3.1.9</span> <span class="content"><span>[LWG3646]</span> <code class="highlight"><c- n>ranges</c-><c- o>::</c-><c- n>view_interface</c-><c- o>::</c-><c- n>size</c-></code> Returns A Signed Type</span></a>
        <li><a href="#p2520r0-move_iterator-should-be-a-random-access-iterator"><span class="secno">3.1.10</span> <span class="content"><span>[P2520R0]</span> <code class="highlight"><c- n>move_iterator</c-></code> Should Be A Random Access Iterator</span></a>
        <li><a href="#p2499r0-string_view-range-constructor-should-be-explicit"><span class="secno">3.1.11</span> <span class="content"><span>[P2499R0]</span> <code class="highlight"><c- n>string_view</c-></code> Range Constructor Should Be Explicit</span></a>
        <li><a href="#p2549r0-unexpected-should-have-error-as-member-accessor"><span class="secno">3.1.12</span> <span class="content"><span>[P2549R0]</span> <code class="highlight"><c- n>unexpected</c-></code> Should Have <code class="highlight"><c- n>error</c-></code> As Member Accessor</span></a>
        <li><a href="#p2517r0-add-a-conditional-noexcept-specification-to-apply"><span class="secno">3.1.13</span> <span class="content"><span>[P2517R0]</span> Add A Conditional <code class="highlight"><c- k>noexcept</c-></code> Specification To <code class="highlight"><c- n>apply</c-></code></span></a>
       </ol>
      <li>
       <a href="#polls-cpp26-and-ts"><span class="secno">3.2</span> <span class="content">C++26 and Technical Specification Polls</span></a>
       <ol class="toc">
        <li><a href="#p2300r5-stdexecution"><span class="secno">3.2.1</span> <span class="content"><span>[P2300R5]</span> <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>execution</c-></code></span></a>
        <li><a href="#p1083r5-resource_adaptor"><span class="secno">3.2.2</span> <span class="content"><span>[P1083R5]</span> <code class="highlight"><c- n>resource_adaptor</c-></code></span></a>
        <li><a href="#p1202r4-asymmetric-fences"><span class="secno">3.2.3</span> <span class="content"><span>[P1202R4]</span> Asymmetric Fences</span></a>
       </ol>
     </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 2022-05, the C++ Library Evolution group conducted a series of
  electronic decision polls <a data-link-type="biblio" href="https://wg21.link/p2574r0">[P2574R0]</a>.
This paper provides the results of those polls and summarizes the results.</p>
   <p>In total, 34 people participated in the polls.
Some participants opted to not vote on some polls.
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 style="padding-bottom: 10px;">Poll 
      <th>SF 
      <th>WF 
      <th>N 
      <th>WA 
      <th>SA 
      <th>Outcome 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.1: Return <a data-link-type="biblio" href="https://wg21.link/p1885r10">[P1885R10]</a> Naming Text Encodings to Demystify Them to Library Working Group for C++23, classified as an addition (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 3 item). 
      <td>6 
      <td>11 
      <td>2 
      <td>0 
      <td>1 
      <td>Consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.2: Return <a data-link-type="biblio" href="https://wg21.link/p0792r8">[P0792R8]</a> function_ref to Library Working Group for C++23, classified as an addition (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 3 item). 
      <td>11 
      <td>10 
      <td>1 
      <td>1 
      <td>1 
      <td>Consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.3: Return <a data-link-type="biblio" href="https://wg21.link/p1223r3">[P1223R3]</a> find_last to Library Working Group for C++23, classified as an addition (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 3 item). 
      <td>13 
      <td>9 
      <td>1 
      <td>1 
      <td>0 
      <td>Consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.4: Send <a data-link-type="biblio" href="https://wg21.link/p1169r3">[P1169R3]</a> Static operator() to Library Working Group for C++23, classified as an addition (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 3 item). 
      <td>13 
      <td>9 
      <td>0 
      <td>0 
      <td>0 
      <td>Unanimous consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.5: Send <a data-link-type="biblio" href="https://wg21.link/p2553r1">[P2553R1]</a> Make mdspan size_type Controllable to Library Working Group for C++23, classified as an improvement of an existing feature (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 2 item). 
      <td>7 
      <td>9 
      <td>1 
      <td>1 
      <td>0 
      <td>Consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.6: Send <a data-link-type="biblio" href="https://wg21.link/p2554r0">[P2554R0]</a> C-Array Interoperability Of mdspan to Library Working Group for C++23, classified as an improvement of an existing feature (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 2 item). 
      <td>6 
      <td>10 
      <td>3 
      <td>0 
      <td>0 
      <td>Strong consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.7: Send <a data-link-type="biblio" href="https://wg21.link/p2540r0">[P2540R0]</a> Empty Product For Certain Views to Library Working Group for C++23, classified as an improvement of an existing feature (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 2 item). 
      <td>7 
      <td>7 
      <td>2 
      <td>2 
      <td>1 
      <td>Weak consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.8: Send <a data-link-type="biblio" href="https://wg21.link/p2538r0">[P2538R0]</a> ADL-Proof projected to Library Working Group for C++23, classified as an improvement of an existing feature (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 2 item). 
      <td>8 
      <td>11 
      <td>2 
      <td>0 
      <td>0 
      <td>Strong consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.9: Send the proposed resoluton in <a data-link-type="biblio" href="https://wg21.link/lwg3646">[LWG3646]</a> ranges::view_interface::size Returns A Signed Type to Library Working Group for C++23, classified as an improvement of an existing feature (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 2 item). 
      <td>10 
      <td>9 
      <td>0 
      <td>0 
      <td>0 
      <td>Unanimous consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.10: Send <a data-link-type="biblio" href="https://wg21.link/p2520r0">[P2520R0]</a> move_iterator Should Be A Random Access Iterator to Library Working Group for C++23, classified as an improvement of an existing feature (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 2 item). 
      <td>12 
      <td>5 
      <td>1 
      <td>0 
      <td>0 
      <td>Strong consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.11: Send <a data-link-type="biblio" href="https://wg21.link/p2499r0">[P2499R0]</a> string_view Range Constructor Should Be Explicit to Library Working Group for C++23, classified as an improvement of an existing feature (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 2 item). 
      <td>13 
      <td>7 
      <td>1 
      <td>2 
      <td>0 
      <td>Consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.12: Send <a data-link-type="biblio" href="https://wg21.link/p2549r0">[P2549R0]</a> unexpected Should Have error As Member Accessor to Library Working Group for C++23, classified as an improvement of an existing feature (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 2 item). 
      <td>9 
      <td>9 
      <td>2 
      <td>0 
      <td>0 
      <td>Strong consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 1.13: Send <a data-link-type="biblio" href="https://wg21.link/p2517r0">[P2517R0]</a> Add A Conditional noexcept Specification To apply to Library Working Group for C++23, classified as an improvement of an existing feature (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 2 item). 
      <td>14 
      <td>8 
      <td>0 
      <td>0 
      <td>0 
      <td>Unanimous consensus in favor. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 2.1: Send <a data-link-type="biblio" href="https://wg21.link/p2300r5">[P2300R5]</a> std::execution to Library Working Group for C++26, classified as a focus (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 1 item). 
      <td>12 
      <td>6 
      <td>2 
      <td>2 
      <td>3 
      <td>Weak consensus in favor. The Chair, Bryce Adelstein Lelbach, asked Vice Chairs Fabio Fracassi and Ben Craig to determine consensus on this poll, as the Chair is one of the co-authors of P2300. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 2.2: Return <a data-link-type="biblio" href="https://wg21.link/p1083r5">[P1083R5]</a> resource_adaptor to Library Working Group for C++26, classified as an addition (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 3 item). 
      <td>3 
      <td>7 
      <td>1 
      <td>4 
      <td>2 
      <td>No consensus. The paper was not updated to follow Library Evolution guidance, which was the cause of most of the votes against. The authors will be asked to produce a new revision with the requested changes and then we will conduct another vote. 
     <tr>
      <td style="padding-bottom: 16px;"> Poll 2.3: Send <a data-link-type="biblio" href="https://wg21.link/p1202r4">[P1202R4]</a> Asymmetric Fences to Library Working Group for the Concurrency TS v2, classified as an addition (<a data-link-type="biblio" href="https://wg21.link/p0592r4">[P0592R4]</a> bucket 3 item). 
      <td>6 
      <td>8 
      <td>1 
      <td>1 
      <td>0 
      <td>Consensus in favor. 
   </table>
   <h2 class="heading settled" data-level="3" id="selected-poll-comments"><span class="secno">3. </span><span class="content">Selected Poll Comments</span><a class="self-link" href="#selected-poll-comments"></a></h2>
   <h3 class="heading settled" data-level="3.1" id="polls-cpp23"><span class="secno">3.1. </span><span class="content">C++23 Polls</span><a class="self-link" href="#polls-cpp23"></a></h3>
   <h4 class="heading settled" data-level="3.1.1" id="p1885r10-naming-text-encodings-to-demystify-them"><span class="secno">3.1.1. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p1885r10">[P1885R10]</a> Naming Text Encodings to Demystify Them</span><a class="self-link" href="#p1885r10-naming-text-encodings-to-demystify-them"></a></h4>
   <blockquote>
    <p>We need this for proper portability</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Improving unicode support is a very important endeavour for C++</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>It’s clearly a useful feature. I was being held back by the question of what to do when CHAR_BIT != 8, but I found an answer in the proposal. I’m unsure the proposed resolution to that issue is ideal, but it’s workable so I can do with it.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>My objections to the prior version of the paper have been addressed by restricting the scope to narrow encodings.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>The removal of the wide encodings (which were really still byte encodings) remedies the major issues with the previous revision.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I remain dissatisfied with the incoherently capitalized constants. (Can someone explain why the T in "Unknown8BiT" is capitalized?)</p>
    <p>— Neutral</p>
   </blockquote>
   <blockquote>
    <p>Useful, but I’m a bit  concerned about the implementation burden for implementation that support multiple platforms. Much too late to review this in time for C++23 though.</p>
    <p>— Strongly Against</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.1.2" id="p0792r8-function_ref"><span class="secno">3.1.2. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p0792r8">[P0792R8]</a> <code class="highlight"><c- n>function_ref</c-></code></span><a class="self-link" href="#p0792r8-function_ref"></a></h4>
   <blockquote>
    <p>Useful functionality especially when one doesn’t want to convert otherwise-non-template code to template code just to accept an invocable.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This is directly useful to my customers, who tend to roll out their own version in practice.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This is an essential building block that has widespread industry use - we shouldn’t fail to standardize existing practice. Especially if it is such a handy low-cost abstraction.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>I suppose it’s fine to get this in now in this form, but the enhancements in p2472r look very attractive.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>The adjustments for prvalue initializers have made this facility as good as the best of the public implementations of similar features, although dangling is still possible by assigning to, say, a std::function_ref member variable.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I have mixed feeling.
History tells us non-trivially copy-able types are generally less useful, but only supporting function pointer is limiting in terns of API, and i don’t know if we have enough visibility on the recent changes</p>
    <p>— Neutral</p>
   </blockquote>
   <blockquote>
    <p>Uncertain whether we’ve ended up with the right design, after a lot of changes and footgun removal. I think it’s too late to be sure about it, would be safer to aim for C++26.</p>
    <p>— Weakly Against</p>
   </blockquote>
   <blockquote>
    <p>Disallowing member pointers is inconsistent with almost everything we’ve added to the standard library since C++11; see, e.g., function, bind(/_front/_back), move_only_function, reference_wrapper, not_fn, apply, thread, all the ranges algorithms and views, etc.</p>
    <p>Sure, to maintain the size at &lt;= 2 pointers would require storing (at least PMFs) by reference, and hence lead to potential dangling in the case of misuse. But so does using a simple lambda. This feature has sharp edges by design; banning member pointers doesn’t meaningfully reduce them, only adds a gratuitous inconsistency.</p>
    <p>And if we want to reduce dangling errors, why aren’t we storing sufficiently small trivially copyable types by value?</p>
    <p>— Strongly Against</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.1.3" id="p1223r3-find_last"><span class="secno">3.1.3. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p1223r3">[P1223R3]</a> <code class="highlight"><c- n>find_last</c-></code></span><a class="self-link" href="#p1223r3-find_last"></a></h4>
   <blockquote>
    <p>It clears many back and forth arithmetics on the paper when using reversed iterators.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>find_last() is is clear compared to the code required without it.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>We have this already as e.g. a std::string member function. It is generally useful, so should be provided.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Support for sentinels is already an improvement over the reverse_iterator approach (which would have to convert them first); returning the end iterator is an additional aspect that would be cumbersome to reimplement.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I’m not super convinced by the return type change (this seems similar to the catamorphic algorithms for which we don’t usually return the past-the-end iterator despite necessarily computing it - see e.g., min/max/minmax, count, etc.), but not enough to vote against.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Whilst find_last enables no new functionality, the paper does a good job illustrating the inherent complexity of using reverse_iterator. This “new” algorithm vastly improves readability. Following the principle of useful returns is a good reason to introduce a return type inconsistency, even if the supplied information is rarely used.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Too late, no time to review it.</p>
    <p>— Weakly Against</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.1.4" id="p1169r3-static-operator"><span class="secno">3.1.4. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p1169r3">[P1169R3]</a> Static <code class="highlight"><c- k>operator</c-><c- p>()</c-></code></span><a class="self-link" href="#p1169r3-static-operator"></a></h4>
   <blockquote>
    <p>Enabling additional optimizations by removing redundant instructions is a big win to me. Unfortunately this has to be an explicit opt-in, which prevents a slew of existing functors from exploiting this. The mentioned library changes (deduction guides) must also be applied to function_ref and move_only_function!</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>The benefits are direct for the people I work with. There have been questions about per-compiler codegen on the reflectors, but I think our vendors can find solutions were there were potential issues.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>It was always an unnecessary restriction to prevent call operators from being static.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>If operator() doesn’t require an object it shouldn’t need to be non-static.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>The language feature is useful, even if it adds another wrong default, and the library support for it is straightforward and correct (although std::function_ref may need work for it).</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I’ve wanted this for years. The proposal seems solid. Won’t take much time to review.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>It’s unfortunate that we can’t make lambdas handle this automatically, but I still want this and the potentially better code generated as a result.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.1.5" id="p2553r1-make-mdspan-size_type-controllable"><span class="secno">3.1.5. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p2553r1">[P2553R1]</a> Make <code class="highlight"><c- n>mdspan</c-></code> <code class="highlight"><c- n>size_type</c-></code> Controllable</span><a class="self-link" href="#p2553r1-make-mdspan-size_type-controllable"></a></h4>
   <blockquote>
    <p>Thanks for measuring real-world programs.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>The rationale makes sense, and the proposal is based on real-world experience from the expected user base. We want this feature to be used.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>
     This is a very important feature for mdspan in the context of non-CPU accelerators like GPUs and FPGAs. I recently implemented such a feature in a library with similar capabilities to mdspan and with similar design choices (my library also has something like extents
     <sizetypeU0002C U0002E...>). It integrated well and proofed beneficial.</sizetypeU0002C>
    </p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>The application domains for mdspan definitely include contexts where the width of an index is an important performance consideration.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Too late, no time to review it.</p>
    <p>— Weakly Against</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.1.6" id="p2554r0-c-array-interoperability-of-mdspan"><span class="secno">3.1.6. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p2554r0">[P2554R0]</a> C-Array Interoperability Of <code class="highlight"><c- n>mdspan</c-></code></span><a class="self-link" href="#p2554r0-c-array-interoperability-of-mdspan"></a></h4>
   <blockquote>
    <p>This paper is elegant in improving C++23 behaviour for immediate benefit, while also opening the door to extending mdspan capabilities if core language changes in the future.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>mdspan should support rank-1 C arrays.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This removes a pitfall in mdspan initialization (providing the correct behavior in one case and trapping in another).  It contains an obvious omission in the Pointer&amp; deduction guide, but there’s no design question there.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This needs quick fixing and avoids a trap with mdspan. The paper seems a bit rushed though, like the paper number still being PXXXX.
Furthermore, I am also surprised by the second deduction guide deducing a zero-dimensional mdspan from a pointer. This seems logical, but the paper lacks motivation for that change.
Anyway, I still approve this fix.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>It seems like a win, but a small one. I’ll still take it, but I feel we have to find a better solution overall.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I consider raw arrays a complete waste of time, but I’m not opposed to this proposal.</p>
    <p>— Neutral</p>
   </blockquote>
   <blockquote>
    <p>This can be added later,</p>
    <p>— Neutral</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.1.7" id="p2540r0-empty-product-for-certain-views"><span class="secno">3.1.7. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p2540r0">[P2540R0]</a> Empty Product For Certain Views</span><a class="self-link" href="#p2540r0-empty-product-for-certain-views"></a></h4>
   <blockquote>
    <p>This improvement will increase coherence</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>While the mathematically correct empty case for std::zip is impractical, that for std::cartesian_product is reasonable and therefore needful.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This change makes an <code class="highlight"><c- n>cartesian_product</c-></code> return a more sensible and mathematically consistent result.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Makes sense, although I cannot be SF of this w/o wording.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>While the paper offers a compelling mathematical argument, it does not illustrate with example how the proposed changed improves composition with other view, which is the question.
It is not clear to me that there is a use case for a product of empty view either.
As all the possible solutions do seem equally (un)motivated, this looks as reasonable as anything.</p>
    <p>— Neutral</p>
   </blockquote>
   <blockquote>
    <p>While this does have some mathematical basis, I am not convinced that this is a usability improvement for the adapter.</p>
    <p>— Weakly Against</p>
   </blockquote>
   <blockquote>
    <p>This paper does not have the wording. It is minimal but yet was not provided before the vote.</p>
    <p>— Weakly Against</p>
   </blockquote>
   <blockquote>
    <p>The paper/revision in question has no wording.</p>
    <p>— Strongly Against</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.1.8" id="p2538r0-adl-proof-projected"><span class="secno">3.1.8. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p2538r0">[P2538R0]</a> ADL-Proof <code class="highlight"><c- n>projected</c-></code></span><a class="self-link" href="#p2538r0-adl-proof-projected"></a></h4>
   <blockquote>
    <p>This restores parity between ranges and old versions of algorithms.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Making the library more usable in edge cases is a good thing.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This fixes an unfortunate case from the current specification</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This looks like an elegant solution to a complex problem, although it relies on a darker corner of the language.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>
     It’s an unfortunate reality that types like Holder
     <incomplete>* trigger instantiation of the class - and hence hard errors - at the drop of a hat. This paper tries to work around one aspect of the problem - which is fine - but doesn’t solve the whole problem.</incomplete>
    </p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>A general feature to control the set of associated entities (or one of the various "tame ADL" proposals) might be a better goal, but there’s no harm done by implementing this carefully now (aside from yet-longer symbol names).</p>
    <p>There is an R1, although it doesn’t seem to contain any technical changes.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.1.9" id="lwg3646-rangesview_interfacesize-returns-a-signed-type"><span class="secno">3.1.9. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/lwg3646">[LWG3646]</a> <code class="highlight"><c- n>ranges</c-><c- o>::</c-><c- n>view_interface</c-><c- o>::</c-><c- n>size</c-></code> Returns A Signed Type</span><a class="self-link" href="#lwg3646-rangesview_interfacesize-returns-a-signed-type"></a></h4>
   <blockquote>
    <p>All sizes should be unsigned for consistency</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>We should apply the results of unsigned/signed discussions consistently.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Whether or not sizes should be represented with unsigned types, at this point we should stay consistent with our established practice and fix outliers.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>I believe this generalizes the interface</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>For better or worse, we’ve been defaulting to unsigned sizes for the ranges provided by the standard library, so we should be consistent.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.1.10" id="p2520r0-move_iterator-should-be-a-random-access-iterator"><span class="secno">3.1.10. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p2520r0">[P2520R0]</a> <code class="highlight"><c- n>move_iterator</c-></code> Should Be A Random Access Iterator</span><a class="self-link" href="#p2520r0-move_iterator-should-be-a-random-access-iterator"></a></h4>
   <blockquote>
    <p>Iterators category describe how iterators can move over a sequence, which is a property of the sequence itself, not its elements. As such, the proposed change makes perfect sense.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This will make ranges code that uses moves better.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Doing otherwise is inconsistent with status quo and other similar cases.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Making move_iterator input doesn’t seem to solve any problems - even input iterators can be dereferenced multiple times as long as the iterator isn’t modified (or otherwise invalidated) - only creates new ones.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>If anyone wants to distinguish xvalue ranges (a prvalue range is already at best an input_range if it can’t recompute a value), they’re welcome to do so, but the iterator_category is the wrong tool for that purpose.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.1.11" id="p2499r0-string_view-range-constructor-should-be-explicit"><span class="secno">3.1.11. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p2499r0">[P2499R0]</a> <code class="highlight"><c- n>string_view</c-></code> Range Constructor Should Be Explicit</span><a class="self-link" href="#p2499r0-string_view-range-constructor-should-be-explicit"></a></h4>
   <blockquote>
    <p>Without this fix, there are many libraries and applications where it will not be possible to use string_view.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>The potential pitfall mentioned in the paper is very real. At the same time this range constructor is quite handy. When usability (reduced typing) and safety conflict we should prefer safety.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>This converting constructor is a silent semantic promotion. It should have been explicit to start with.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>I think this is the correct change, it preserves users to have simple syntax to convert to string_view, while avoiding surprising semantics.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>More explicit constructors is generally good, but I feel like explicitly converting to string_view is a nuisance. On balance I think the former wins out here.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>As the person who added that infamous constructor,  I have concerns that</p>
    <ul>
     <li data-md>
      <p>
       This hurts composability of views - which can be mitigated by adding a generic adaptor that calls an explicit constructor in a generic manner (view | std::view::as
       <string_view> | ... )</string_view>
      </p>
     <li data-md>
      <p>
       We are ascribing to string_view and strings more meaning that they can possibly provide to provide. string and vector only differ by their names and a null-terminator, and the motivation for this paper - breakage in fmt - do call for a better solution. That string_view is displayed as a string, but QLatin1String isn’t and span
       <char8_t>
         doesn’t even compile is interesting, to say the list. Not sure that preventing a vector
        <char> to be convertible to string_view is the solution.</char>
       </char8_t>
      </p>
    </ul>
    <p>That being said, by my own logic, string_view is redundant with span - the only sailent difference is the constness of string_view, and there was very strong support for a change of direction, and very little support for my eccentric views on strings.</p>
    <p>And this is miles better than just removing the constructor all together.
Ship it.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>The confusion still exists, just not implicitly.</p>
    <p>— Weakly Against</p>
   </blockquote>
   <blockquote>
    <p>The poll fails to specify which option is being taken, although the minutes imply it’s Option 1.</p>
    <p>The potential pitfalls outlined in the paper are real, but the fact that char* is special (and that arrays can decay but std::array cannot) is hardly news to anyone doing string processing in C++.  Converting a std::string to a std::string_view doesn’t stop at any included null, and so it should not surprise anyone that converting any other container behaves the same way.</p>
    <p>— Weakly Against</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.1.12" id="p2549r0-unexpected-should-have-error-as-member-accessor"><span class="secno">3.1.12. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p2549r0">[P2549R0]</a> <code class="highlight"><c- n>unexpected</c-></code> Should Have <code class="highlight"><c- n>error</c-></code> As Member Accessor</span><a class="self-link" href="#p2549r0-unexpected-should-have-error-as-member-accessor"></a></h4>
   <blockquote>
    <p>I believe error() is the better name as it makes the code clarity less dependent on the name of the object it’s called on.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>It makes more sense for the accessor of a type that’s meant to contain only errors to be error(). value() seems like a misnomer.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>It makes sense, but the status quo would have been manageable for my customers. As long as we pick one...</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>Yes, this is slightly better, although i still don’t understand the motivation for unexpected to have any public member</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>
     I am convinced by the argument that unexpected is a type-safe cousin to expected
     <eU0002C t> where we statically know the contained value is an error.</eU0002C>
    </p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I’m not convinced by the rationale as I think it relies on false equivalences, but I don’t really care</p>
    <p>— Neutral</p>
   </blockquote>
   <blockquote>
    <p>It can be argued that consistency is improved by this change, but it should be rare to use std::unexpected except as a tag and even rarer to use it in a generic context where the name really matters.</p>
    <p>— Neutral</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.1.13" id="p2517r0-add-a-conditional-noexcept-specification-to-apply"><span class="secno">3.1.13. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p2517r0">[P2517R0]</a> Add A Conditional <code class="highlight"><c- k>noexcept</c-></code> Specification To <code class="highlight"><c- n>apply</c-></code></span><a class="self-link" href="#p2517r0-add-a-conditional-noexcept-specification-to-apply"></a></h4>
   <blockquote>
    <p>A very nice fix, the noexceptness of such facilities should preferably be transparent.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>We already applying conditional noexcept for most of the functional part of the standard library, and this makes it consistent.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Missing a link in the conditional noexcept chain throws off the noexcept-ness of downstream consumers.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>The zip family should be implementable using apply.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>It’s obviously correct for all the call wrappers to forward as many properties as possible (even if we wish the language made this easier).</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I’m not convinced by the motivation. The use of apply in the example doesn’t seem materially different from the use of the lambda, which doesn’t have a noexcept specification either.</p>
    <p>This is close to mandating QoI. I see no real drawbacks but also not much point.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <h3 class="heading settled" data-level="3.2" id="polls-cpp26-and-ts"><span class="secno">3.2. </span><span class="content">C++26 and Technical Specification Polls</span><a class="self-link" href="#polls-cpp26-and-ts"></a></h3>
   <h4 class="heading settled" data-level="3.2.1" id="p2300r5-stdexecution"><span class="secno">3.2.1. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p2300r5">[P2300R5]</a> <code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>execution</c-></code></span><a class="self-link" href="#p2300r5-stdexecution"></a></h4>
   <blockquote>
    <p>Getting this in early in the 26 cycle will make it available as the basis of further work and will give us time to find and fix any issues that arise.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>We need this as the basis for further work. Unless we settle on this (preferably in plenary) as the status quo we will "discuss in circles" forever.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>We really need this ASAP. It was unfortunate it missed C++23</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>While the concerns about its readiness for C++23 were quite reasonable, it seems to have been established that this system is appropriately efficient and generic to be the foundation for C++26 structured concurrency even if almost all use will be by wrappers yet to be devised.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I’m not seeing the point of sending this right now to languish in LWG’s queue until next February.</p>
    <p>— Neutral</p>
   </blockquote>
   <blockquote>
    <p>I want to believe that get_delegatee_scheduler addresses one of my major objections to this paper: Lack of the ability to explicitly break cyclic graphs and thereby support reentrancy but the description/definition is so vague that I can’t tell if it actually addresses this concern or I’m just reading into it what I want to see.</p>
    <p>Moreover I continue to have concerns with the speed with which this paper is being pushed/forwarded: The version we’re voting to forward wasn’t even available through wg21.link when polling opened, for example.</p>
    <p>— Weakly Against</p>
   </blockquote>
   <blockquote>
    <p>I believe that further revision is needed in order to better correlate P2300 with the relevant papers:</p>
    <ul>
     <li data-md>
      <p>The async_scope proposal seems to be a better mechanism for spawning work than ensure_started and start_detached.</p>
     <li data-md>
      <p>It is not yet clear how the standard library algorithms will be overloaded to work with std::execution.</p>
     <li data-md>
      <p>The system execution context integration is not fully designed.</p>
    </ul>
    <p>
     On the other hand, it seems that P2300’s additions to the 
     <functional> header (primarily, tag_invoke) would be better suited for a more general separate paper.</functional>
    </p>
    <p>— Strongly Against</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.2.2" id="p1083r5-resource_adaptor"><span class="secno">3.2.2. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p1083r5">[P1083R5]</a> <code class="highlight"><c- n>resource_adaptor</c-></code></span><a class="self-link" href="#p1083r5-resource_adaptor"></a></h4>
   <blockquote>
    <p>Adapting a non-polymorphic allocator to a pmr is functionality that ought to be put into the standard.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>The issue that LWG noted has been addressed and the reasons for moving this into the working draft remain.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>I can see the use case, we still need to finalize some of the details (which can be finalized by C++26’s deadline)</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I do not have strong opinion, however I do want std::aligned_raw_storage, as an improvement over deprecated std::aligned_storage</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>I need aligned_raw_storage like yesterday. aligned_object_storage seems not designed for polymorphic types.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>As stated, this is missing the changes suggested during the LEWG review. In particular, it’s not clear that the design of aligned_object_storage is the right one.</p>
    <p>— Weakly Against</p>
   </blockquote>
   <blockquote>
    <p>Not sure the design is right yet, it’s still in flux.</p>
    <p>— Weakly Against</p>
   </blockquote>
   <blockquote>
    <p>This facility should not be standardized. Its claims about what is or is not a vocabulary type are questionable, and polymorphic_allocator has loads of problems in and of itself, and turning actual allocators into memory resources has more. The standard doesn’t need to and shouldn’t encourage hacks like this, it should rather suggest that allocator-aware types be written as templates, so that they are actually customizable wrt. allocation, which memory resources or single-never-fits-all non-vocabulary types do not achieve.</p>
    <p>— Strongly Against</p>
   </blockquote>
   <blockquote>
    <p>This revision R5 up for vote does not reflect LEWG guidance from the forwarding poll; the forwarding poll was conditional on implementing such guidance.</p>
    <p>— Strongly Against</p>
   </blockquote>
   <h4 class="heading settled" data-level="3.2.3" id="p1202r4-asymmetric-fences"><span class="secno">3.2.3. </span><span class="content"><a data-link-type="biblio" href="https://wg21.link/p1202r4">[P1202R4]</a> Asymmetric Fences</span><a class="self-link" href="#p1202r4-asymmetric-fences"></a></h4>
   <blockquote>
    <p>I believe that the benefits of this additional synchronization primitives need to be confirmed, and TS is correct vehicle for them.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>The design here is simple and satisfactory, and already unanimously approved before. The only changes are those dictated by P2396, which was also unanimously approved. This is useful functionality for the TS.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>Despite my reservations about library TSs, I think we should get wider experience and feedback with asymmetric fences  and the TS is not inappropriate.</p>
    <p>— Strongly Favor</p>
   </blockquote>
   <blockquote>
    <p>I want this feature to make progress into TS2, even though I do not fully understand its uses</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>It seems reasonable, but I was not there for the discussions so I cannot take a stronger stance.</p>
    <p>— Weakly Favor</p>
   </blockquote>
   <blockquote>
    <p>No mention of implementation experience, or what is required (is it a pure library proposal? Presumably not if it will require changes to the compiler’s memory model?)</p>
    <p>— Weakly Against</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-lwg3646">[LWG3646]
   <dd>Jiang An. <a href="https://wg21.link/lwg3646"><cite>std::ranges::view_interface::size returns a signed type</cite></a>. LEWG. URL: <a href="https://wg21.link/lwg3646">https://wg21.link/lwg3646</a>
   <dt id="biblio-p0592r4">[P0592R4]
   <dd>Ville Voutilainen. <a href="https://wg21.link/p0592r4"><cite>To boldly suggest an overall plan for C++23</cite></a>. 25 November 2019. URL: <a href="https://wg21.link/p0592r4">https://wg21.link/p0592r4</a>
   <dt id="biblio-p0792r8">[P0792R8]
   <dd>Vittorio Romeo, Zhihao Yuan, Jarrad Waterloo. <a href="https://wg21.link/p0792r8"><cite>function_ref: a non-owning reference to a Callable</cite></a>. 16 February 2022. URL: <a href="https://wg21.link/p0792r8">https://wg21.link/p0792r8</a>
   <dt id="biblio-p1083r5">[P1083R5]
   <dd>Pablo Halpern. <a href="https://wg21.link/p1083r5"><cite>Move resource_adaptor from Library TS to the C++ WP</cite></a>. 24 February 2022. URL: <a href="https://wg21.link/p1083r5">https://wg21.link/p1083r5</a>
   <dt id="biblio-p1169r3">[P1169R3]
   <dd>Barry Revzin, Casey Carter. <a href="https://wg21.link/p1169r3"><cite>static operator()</cite></a>. 14 October 2021. URL: <a href="https://wg21.link/p1169r3">https://wg21.link/p1169r3</a>
   <dt id="biblio-p1202r4">[P1202R4]
   <dd>David Goldblatt. <a href="https://wg21.link/p1202r4"><cite>Asymmetric Fences</cite></a>. 15 February 2022. URL: <a href="https://wg21.link/p1202r4">https://wg21.link/p1202r4</a>
   <dt id="biblio-p1223r3">[P1223R3]
   <dd>Zach Laine. <a href="https://wg21.link/p1223r3"><cite>find_last</cite></a>. 15 February 2022. URL: <a href="https://wg21.link/p1223r3">https://wg21.link/p1223r3</a>
   <dt id="biblio-p1885r10">[P1885R10]
   <dd>Corentin Jabot, Peter Brett. <a href="https://wg21.link/p1885r10"><cite>Naming Text Encodings to Demystify Them</cite></a>. 14 February 2022. URL: <a href="https://wg21.link/p1885r10">https://wg21.link/p1885r10</a>
   <dt id="biblio-p2300r5">[P2300R5]
   <dd>Michał Dominiak, Georgy Evtushenko, Lewis Baker, Lucian Radu Teodorescu, Lee Howes, Kirk Shoop, Michael Garland, Eric Niebler, Bryce Adelstein Lelbach. <a href="https://wg21.link/p2300r5"><cite>`std::execution`</cite></a>. 22 April 2022. URL: <a href="https://wg21.link/p2300r5">https://wg21.link/p2300r5</a>
   <dt id="biblio-p2499r0">[P2499R0]
   <dd>James Touton. <a href="https://wg21.link/p2499r0"><cite>string_view range constructor should be explicit</cite></a>. 7 December 2021. URL: <a href="https://wg21.link/p2499r0">https://wg21.link/p2499r0</a>
   <dt id="biblio-p2517r0">[P2517R0]
   <dd>Hewill Kang. <a href="https://wg21.link/p2517r0"><cite>Add a conditional noexcept specification to std::apply</cite></a>. 14 January 2022. URL: <a href="https://wg21.link/p2517r0">https://wg21.link/p2517r0</a>
   <dt id="biblio-p2520r0">[P2520R0]
   <dd>Barry Revzin. <a href="https://wg21.link/p2520r0"><cite>move_iterator should be a random access iterator</cite></a>. 16 January 2022. URL: <a href="https://wg21.link/p2520r0">https://wg21.link/p2520r0</a>
   <dt id="biblio-p2538r0">[P2538R0]
   <dd>Arthur O'Dwyer. <a href="https://wg21.link/p2538r0"><cite>ADL-proof std::projected</cite></a>. 15 February 2022. URL: <a href="https://wg21.link/p2538r0">https://wg21.link/p2538r0</a>
   <dt id="biblio-p2540r0">[P2540R0]
   <dd>Steve Downey. <a href="https://wg21.link/p2540r0"><cite>Empty Product for certain Views</cite></a>. 16 February 2022. URL: <a href="https://wg21.link/p2540r0">https://wg21.link/p2540r0</a>
   <dt id="biblio-p2549r0">[P2549R0]
   <dd>Yihe Li. <a href="https://wg21.link/p2549r0"><cite>std::unexpected should have error() as member accessor</cite></a>. 13 February 2022. URL: <a href="https://wg21.link/p2549r0">https://wg21.link/p2549r0</a>
   <dt id="biblio-p2553r1">[P2553R1]
   <dd>Christian Trott, Damien Lebrun-Grandie, Mark Hoemmen, Dan Sunderland. <a href="https://wg21.link/p2553r1"><cite>Make mdspan size_type controllable</cite></a>. 16 March 2022. URL: <a href="https://wg21.link/p2553r1">https://wg21.link/p2553r1</a>
   <dt id="biblio-p2554r0">[P2554R0]
   <dd>Christian Trott, Damien Lebrun-Grandie, Mark Hoemmen, K. R. Walker, Dan Sunderland. <a href="https://wg21.link/p2554r0"><cite>C-Array Interoperability of MDSpan</cite></a>. 15 February 2022. URL: <a href="https://wg21.link/p2554r0">https://wg21.link/p2554r0</a>
   <dt id="biblio-p2574r0">[P2574R0]
   <dd>Bryce Adelstein Lelbach. <a href="https://wg21.link/p2574r0"><cite>2022-05 Library Evolution Polls</cite></a>. 22 April 2022. URL: <a href="https://wg21.link/p2574r0">https://wg21.link/p2574r0</a>
  </dl>