optional
expected
| optional | expected | |
|---|---|---|
| 5 | 18 | |
| 885 | 1,625 | |
| 0.9% | 3.9% | |
| 0.0 | 6.8 | |
| 10 months ago | 3 months ago | |
| C++ | C++ | |
| Creative Commons Zero v1.0 Universal | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
optional
- Functional Programming in Modern C++: The Imperatives Must Go ā Victor Ciura [video]
-
Backward compatible implementations of newer standards constructs?
For optional I would recommend Sy's implementation - optional
-
What is your preferred solution repeated nullptr checks on smart pointers
One could think of a more fluent interface to deal with smart pointers, similar to what exists in tl optional https://github.com/TartanLlama/optional
-
Assignment for optional<T>
It looks like tl::optional<>.
- Monadic interface for std::optional
expected
- Functional Programming in Modern C++: The Imperatives Must Go ā Victor Ciura [video]
- Functional exception-less error handling with C++23's optional and expected
-
C++23's New Fold Algorithms - C++ Team Blog
On this topic Sy Brand is a guarantee, in fact he did the https://github.com/TartanLlama/expected and several presentation of the subject.
-
What is the status of the monadic operations for std::expected? It seems like they made it into the standard for C++23, but they don't actually seem to be available in the std::expected implementation (in MSVC's STL)
In the meantime, I may use the TartanLlama implementation (here) and plan around replacing it with the real deal in the near future.
-
ADSP Episode 114: Rust, Val, Carbon, ChatGPT & Errors with Barry Revzin!
Sy Brand's tl::expected
-
Daily bit(e) of C++ | Error handling
expected is my favourite little part of cpp23, Iām using it often in codebase with https://github.com/TartanLlama/expected š
- Noticing the the difference in coding when going back to C++
-
What are some cool modern libraries you enjoy using?
outcome and/or expected
- Do you use builder pattern?
-
Why should I have written ZeroMQ in C, not C++ (2012)
Eventually you'll be able to use std::expected in C++23!
https://en.cppreference.com/w/cpp/header/expected
Don't throw exceptions, require the caller to handle errors and propagate them up the stack (everything returns an expected) if they cannot be handled. You are forced to model the error domains instead of just throwing an exception and assuming the caller knows to catch it and do something with it.
Java has checked exceptions, but, Kotlin decided to abandon them.
The nice codebases I have worked on stick to the Result type in Swift or Kotlin. And thus you are forced to 'translate' errors (exceptions?) as described in Alan Griffith's 'Exceptional Java'.
https://accu.org/journals/overload/10/48/griffiths_406/
"If a checked exception is thrown (to indicate an operation failure) by a method in one package it is not to be propagated by a calling method in a second package. Instead the exception is caught and "translated". Translation converts the exception into: an appropriate return status for the method, a checked exception appropriate to the calling package or an unchecked exception recognised by the system. (Translation to another exception type frequently involves "wrapping".)"
If you can't wait for C++23, there's a single header implementation here.
https://github.com/TartanLlama/expected
What are some alternatives?
variant - C++17 `std::variant` for C++11/14/17
libCat - šāā¬ A runtime for C++26 w/out libC or POSIX. Smaller binaries, only arena allocators, SIMD, stronger type safety than STL, and value-based errors!
nonstd-lite - Parent of *-lite repositories, a migration path to post-C++11 features for pre-C++11 environments
AECforWebAssembly - A port of ArithmeticExpressionCompiler from x86 to WebAssembly, so that the programs written in the language can run in a browser. The compiler has been rewritten from JavaScript into C++.
GSL - Guidelines Support Library
cpp-libp2p - C++17 implementation of libp2p