expected
PEGTL
Our great sponsors
expected | PEGTL | |
---|---|---|
18 | 12 | |
1,402 | 1,867 | |
- | 1.8% | |
2.1 | 7.2 | |
4 months ago | 5 days ago | |
C++ | C++ | |
Creative Commons Zero v1.0 Universal | Boost Software License 1.0 |
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.
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
PEGTL
-
Show HN: Matcheroni, a tiny C++20 header library for building lexers/parsers
Very cool, and I like the name!
I'd be interested in reading about how Matcheroni compares with PEGTL and Lexy.
https://github.com/taocpp/PEGTL
-
Use PEGTL to remove my clunky homemade parser
I found a library I wanted to test: Pegtl
-
What are some cool modern libraries you enjoy using?
I like PEGTL
-
Are C/C++ developers allowed to import libraries to make coding easier or are they expected to build every functions and methods from scratch (without importing anything like String.h)?
Sure - libraries that are expected to be entirely self-contained. The one that comes to mind is PEGTL, a parser combinator library that is intended to be embedded inside a larger program. Making it import more dependencies would break this philosophy. Similarly, in the Rust world, there are a variety of "no-std" crates that should be able to be imported even if the standard library is not available on the target platform.
-
TIL: Visual Studio has quantum state values ๐คจ
The program in the post was just an example meant to illustrate the problem. Originally, this (new) behavior of MSVC broke my code in the PEGTL, see [this commit](https://github.com/taocpp/PEGTL/commit/e3c8cb499dc3d1d76d23f2d5d79469dcb15550c5) that I needed to apply to fix it.
-
We Built a C++ Rendering Engine for the Web
As a professional C++ programmer I feel a lot of the reasons C++ gets this response is because it's simply not "batteries included" like Go or Rust.
C++ is a very powerful, unopinionated language, that gives you a lot of freedom to attack your problem domain the way you best see fit.
If you're writing a networked application, don't use POSIX sockets, go and find a higher level library. If you're parsing complex text formats, don't iterate over buffers with char*'s, go pick up PEGTL[0]. If you're working on graphs, or need to properly index in-memory data, go pick up Boost[1][2]. If you need a GUI, go pick up Qt.
It's extremely common in C++, due to the lack of a universal package management solution, for people to try and "muddle through" and do shit themselves when it's far outside their core competency.
At one of my last employers, the core product was parsing JSON with std::regex, simply because they couldn't be bothered to integrate a JSON library.
[0] https://github.com/taocpp/PEGTL
[1] https://www.boost.org/doc/libs/1_76_0/libs/graph/
[2] https://www.boost.org/doc/libs/1_76_0/libs/multi_index/doc/i...
-
Is there anything like sly for C++?
You are looking for Boost.Spirit (https://www.boost.org/doc/libs/1_76_0/libs/spirit/doc/x3/html/index.html) or PEGTL (https://github.com/taocpp/PEGTL)
-
Why no more Lex/Yakk/ANTLR/whatever?
I personally prefer to use parsing combinator libraries in C++, where the "grammar" is just part of normal C++ and directly integrate. Examples are Boost.Spirit, pegtl, or (my own) lexy.
- Rust's Most Unrecognized Contributor
-
Wondered if anyone is interested in a c++ parser combinators library?
While I'm not quite sure how this might transfer to your approach, with your Haskell-inspired style being quite different from our C++ templates, in the PEGTL our equivalent to your Char, which is called one, is variadic (true to the T in PEGTL a variadic template) and takes a list of possible matches.
What are some alternatives?
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!
lexy - C++ parsing DSL
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++.
cpp-peglib - A single file C++ header-only PEG (Parsing Expression Grammars) library
cpp-libp2p - C++17 implementation of libp2p
spirit - Boost.org spirit module
Thrust - [ARCHIVED] The C++ parallel algorithms library. See https://github.com/NVIDIA/cccl
C++ B-tree - Git mirror of the official (mercurial) repository of cpp-btree
magnum - Lightweight and modular C++11 graphics middleware for games and data visualization
pybind11 - Seamless operability between C++11 and Python
stb - stb single-file public domain libraries for C/C++
sparsepp - A fast, memory efficient hash map for C++