mirror of
https://github.com/boostorg/outcome.git
synced 2026-02-20 15:02:09 +00:00
43 lines
2.3 KiB
HTML
43 lines
2.3 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
|
<html><meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
|
<title>Interoperation - Boost.Outcome documentation</title>
|
|
<link rel="stylesheet" href="/boost-outcome/css/boost.css" type="text/css">
|
|
<meta name="generator" content="Hugo with Boostdoc theme">
|
|
<meta name="viewport" content="width=device-width,initial-scale=1.0"/>
|
|
|
|
<link rel="icon" href="/boost-outcome/images/favicon.ico" type="image/ico"/>
|
|
<body><div id="content">
|
|
|
|
<p>This is the final section of the tutorial, and it is unavoidably quite lengthy.</p>
|
|
|
|
<p>One thing which Outcome solves – which alternatives do not – is how to
|
|
<strong>non-intrusively</strong> tie together multiple third party libraries, each using
|
|
Outcome – or some other <code>T|E</code> implementatation like <code>std::expected<T, E></code>
|
|
– with custom incommensurate <code>E</code> types, or indeed arbitrary return
|
|
types which are “split” <code>T|E</code> return types. Solving
|
|
this well is the <em>coup de grâce</em> of Outcome against alternative approaches
|
|
to this problem domain,
|
|
including <code>std::expected<T, E></code>. It is the major reason why you should
|
|
consider using Outcome over alternatives, including Expected.</p>
|
|
|
|
<p>Firstly we shall explore some of the problems faced by the software
|
|
developer when <code>T|E</code> return type based code proliferates at scale,
|
|
where dozens of libraries may be using completely incompatible <code>T|E</code> return types.</p>
|
|
|
|
<p>Secondly we shall introduce the <code>ValueOrError</code> concept support in Outcome
|
|
which implements a subset of the proposed <a href="https://wg21.link/P0786">WG21 <code>ValueOrError</code>
|
|
concept framework</a>.</p>
|
|
|
|
<p>Finally, we shall then step through a worked example which mocks up a realistic
|
|
situation that the software developer may find themselves in: tying
|
|
together disparate third party libraries, whose source code cannot be
|
|
modified, into an application-wide, mixed-mode <code>T|E</code> and exception
|
|
throwing universal error handling system which is capable of
|
|
accurately representing the original failure, but also propagating it
|
|
in a way that the application can deal with universally.</p>
|
|
|
|
|
|
|
|
</div></body>
|
|
</html>
|