Did you know ... | Search Documentation: |
Pack logtalk -- logtalk-3.86.0/manuals/_sources/libraries/expecteds.rst.txt |
.. _library_expecteds:
expecteds
This library provides an implementation of expected terms with an API
that is inspired by the optional
library and C++ standardization
proposals for an Expected<T>
type. An expected term is an opaque
compound term that either contains an expected value or an error
informing why the expected value is not present. Expected terms provide
an alternative to generating an exception (or a failure) when something
unexpected happens when asking for a value. This allows e.g. separating
the code that constructs expected terms from the code that processes
them, which is then free to deal if necessary and at its convenience
with any unexpected events.
Open the `../../docs/library_index.html#expecteds <../../docs/library_index.html#expecteds>`__ link in a web browser.
To load all entities in this library, load the loader.lgt
file:
::
| ?- logtalk_load(expecteds(loader))
.
To test this library predicates, load the tester.lgt
file:
::
| ?- logtalk_load(expecteds(tester))
.
The expected
object provides constructors for expected terms. For
example:
::
| ?- expected::of_expected(1, Expected)
.
...
The created expected terms can then be passed as parameters to the expected/1 parametric object. For example:
::
| ?- expected::of_expected(1, Expected)
, expected(Expected)
::or_else(Value, 0)
.
Expected = expected(1)
,
Value = 1
yes
| ?- expected::of_unexpected(-1, Expected)
, expected(Expected)
::or_else(Value, 0)
.
Expected = unexpected(-1)
,
Value = 0
yes
The either
object provides types and predicates for extended
type-checking and predicates for handling lists of expected terms.
The optionals
library.