compile-time-regular-expressions
outcome
compile-time-regular-expressions | outcome | |
---|---|---|
26 | 9 | |
3,163 | 662 | |
- | - | |
7.0 | 6.9 | |
10 days ago | 5 days ago | |
C++ | C++ | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
compile-time-regular-expressions
-
Why are strings and IO so complicated?
CTRE (https://github.com/hanickadot/compile-time-regular-expressions) ranges::views (filter, transform, etc.) (C++20) str.find() + str.substr() freopen to stdin + cin >> extraction Parser libraries
- Compile time regular expression in C++
-
What are thoughts on removing regular expression from the standard library?
There are suggestions that should be replaced by the high performance ctre implementation: https://github.com/hanickadot/compile-time-regular-expressions
-
What's the most hilarious use of operator overloading you've seen?
operator"" can be used in a similar way to expression templates (DSLs), where the type of the resulting expression is dependent on the string contents. For example ctre makes use of this to build efficient regular expression parsers, and kumi uses this in conjunction with operator[] to make tuple indexing quite elegant
-
It's easy, I swear! Once you learn a bit about it, you'll be amazed!
Check out https://github.com/hanickadot/compile-time-regular-expressions anything is possible 😂
-
Verify all characters are same except a few
Yes to regex, no to std::regex. Better to use CTRE. Something like "^Hello [0-9]+ how are you" should allow checking if there's a match
-
Constexpr regex parser!
You could compare your implementation with https://github.com/hanickadot/compile-time-regular-expressions and see if there are any ideas you can copy.
- Regex is comically slow. High performance alternatives? (Pattern matching for validation)
-
Regex shootout updated - hyperscan 1st, Rust 2nd, std::regex dead last
std::compile_time_regex would be a nice addition. Something similar to ctre https://github.com/hanickadot/compile-time-regular-expressions Simply letting the compiler generate all the regex parsing machinery at compile time.... And benefitting from compiler optimizations, vectorization, etc...
-
What are some cool modern libraries you enjoy using?
ctre
outcome
-
How to define API stability for a C++ library?
https://github.com/ned14/outcome/tree/develop/abi-compliance uses both in a CI pass to ensure Outcome never changes anything which breaks either API or ABI with earlier versions.
-
What are some cool modern libraries you enjoy using?
outcome and/or expected
-
Outcome enters sustaining phase, goes ABI stable
A "Sample Usage" appears on the front page of the docs: https://ned14.github.io/outcome/
-
Does Anyone Use Boost Outcome?
I recently came across boost outcome as I was searching for a better error handling method. It took me a minute to get a hang of it but now I love it. After creating my own policy and a few aliases for easier use.
-
Is this error handling strategy good?
std::optional and std::variant can be a bit awkward to use in this scenario, though. Consider a dedicated type like boost::outcome (standalone versions) or one of the implementations of the proposed std::expected.
-
Modern C++ "result" type based on Swift / Rust
Minimum possible compile time impact is a key goal of https://github.com/ned14/outcome. We ship a single header edition which only includes the low impact standard headers as listed at https://github.com/ned14/stl-header-heft. We also don't use union storage for non-TC non-MB types in order to avoid complex metaprogramming execution by the compiler per instantiation.
-
C++ Memory Safety
It's really weird that I wrote the above, and then this bug was reported to Outcome: https://github.com/ned14/outcome/issues/244. Here is my exact complaint about lack of lifetime tracking in C++.
What are some alternatives?
RE2 - RE2 is a fast, safe, thread-friendly alternative to backtracking regular expression engines like those used in PCRE, Perl, and Python. It is a C++ library.
leaf - Lightweight Error Augmentation Framework
consteval-huffman - Compile-time Huffman coding compression using C++20
C++ Format - A modern formatting library
xorstr - heavily vectorized c++17 compile time string encryption.
Experimental Boost.DI - C++14 Dependency Injection Library
neo-fun - Some library components that didn't quite fit anywhere else...
stb - stb single-file public domain libraries for C/C++
Serial Communication Library - Cross-platform, Serial Port library written in C++
staticvec - Implements a fixed-capacity stack-allocated Vec alternative backed by an array, using const generics.
ZXing - ZXing ("Zebra Crossing") barcode scanning library for Java, Android