<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
        "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
	<title>Merge the Concepts TS Working Draft into the C++20 working draft</title>

	<style>
	p {text-align:justify}
	li {text-align:justify}
	blockquote.note
	{
		background-color:#E0E0E0;
		padding-left: 15px;
		padding-right: 15px;
		padding-top: 1px;
		padding-bottom: 1px;
	}
	ins {color:#00A000}
	del {color:#A00000}
	</style>
</head>
<body>

<address align=right>
Document number: P0724R0
<br/>
Audience: WG21
<br/>
<br/>
<a href="mailto:ville.voutilainen@gmail.com">Ville Voutilainen</a><br/>
2017-06-27<br/>
</address>
<hr/>
<h1 align=center>Merge the Concepts TS Working Draft into the C++20 working draft</h1>

<h2>Abstract</h2>
<p>
  Due to various force-majeure travel reasons, I personally managed to miss the
  weekend before the mailing deadline and the deadline itself, so it was brought
  to my attention a tad too late that nobody wrote this proposal paper. So here goes.
</p>
<p>The proposal is to merge the Concepts TS Working Draft into the C++20
  Working Draft as is, and fix remaining issues, including design issues,
  before the publication of C++20.</p>

<h2>Wording</h2>
<p>
  According to the Concepts TS Editor's report, the current TS has been
  rebased to apply to the C++20 working draft. The TS draft is in the
  pre-Toronto mailing:
</p>
<p>
  <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/n4674.pdf">Working Draft, C++ extensions for Concepts</a>
</p>

<h2>How is this not premature? There are design controversies?</h2>

<p>
  I am well aware of that, but I'm boldly suggesting that we take a brave
  step and send a message to the C++ community that we are serious about
  having Concepts in C++20. In fact, a leap so brave that we merge the
  current wording in and all commit to finishing it up design-wise,
  wording-wise and otherwise before C++20 goes out, without missing
  its schedule.
</p>
<p>
  I'm also well aware that we don't usually merge new wording which has
  known issues (except when we do, but that happens much more rarely
  for Core than Library). Perhaps this facility is significant enough
  to make an exception.
</p>

</body>

</html>
