feedc0de/boost_optional
1
0
Fork 0
forked from boostorg/optional
Code Pull Requests Activity

misused "precedence" changed to "precedent"

Browse Source 
[SVN r35831]
This commit is contained in:
Dave Abrahams
2006-11-04 02:13:53 +00:00
parent 4599ae0bfd
commit 5182283649
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/optional.html
View File

@ -127,7 +127,7 @@ undefined behavior</i>
which in our case is either <code>T</code> or <code>nil_t</code>.<br> which in our case is either <code>T</code> or <code>nil_t</code>.<br>
Using the <a href="../../../doc/html/variant.html">Boost.Variant</a> library, this model can be implemented Using the <a href="../../../doc/html/variant.html">Boost.Variant</a> library, this model can be implemented
in terms of <code>boost::variant&lt;T,nil_t&gt;</code>.<br> in terms of <code>boost::variant&lt;T,nil_t&gt;</code>.<br>
There is precedence for a discriminated union as a model for an optional value: the There is precedent for a discriminated union as a model for an optional value: the
<a href="http://www.haskell.org/"><u>Haskell</u></a> <b>Maybe</b> built-in type constructor. <a href="http://www.haskell.org/"><u>Haskell</u></a> <b>Maybe</b> built-in type constructor.
Thus, a discriminated union <code>T+nil_t</code> serves as a conceptual foundation.</p> Thus, a discriminated union <code>T+nil_t</code> serves as a conceptual foundation.</p>
<p>A <code>variant&lt;T,nil_t&gt;</code> follows naturally from the traditional idiom of extending <p>A <code>variant&lt;T,nil_t&gt;</code> follows naturally from the traditional idiom of extending