range-v3
STL
range-v3 | STL | |
---|---|---|
19 | 154 | |
4,015 | 9,732 | |
- | 1.1% | |
4.0 | 9.7 | |
9 days ago | 4 days ago | |
C++ | C++ | |
GNU General Public License v3.0 or later | 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.
range-v3
-
Why are strings and IO so complicated?
std::ranges is in c++20, but you can pull in the library it was based on if you use 17 (https://github.com/ericniebler/range-v3)
-
Java Streams in c++
What you are describing seems to be std::ranges. If you’re interested in understanding how to implement it, I recommend checking out the original reference implementation, rangev3. Trying to implement your own ranges framework is really good practice for learning how to do efficient, advanced generic programming in C++. I highly recommend it as a hobby learning project. But it’s also really, really hard to do correctly, so please just use the stdlib and/or rangev3 in any real project.
-
What are some of the ways to make a super nasty nested loop become clean?
In C++23, there will be std::views::cartesian_product. It is already available in the range-v3 library, the one that the standard is based on.
- 295 pages on Initialization in Modern C++ :)
-
Function composition in modern C++
/** * @brief Forwards value equivalent to the std::forward. * * Using cast instead of std::forward to avoid template instantiation. Used by * Eric Niebler in range library. * * @see https://github.com/ericniebler/range-v3 */
- PocketPy: A Lightweight(~5000 LOC) Python Implementation in C++17
-
Is there an <algorithm> way to filter + transform multiple containers at once
It uses a custom zip_iterator (which isn't very good, and you should really use the one from boost or from range-v3).
-
what annoys you most while using c++?
It contains very little functionality compared to the Eric Niebler’s reference implementation for my liking. Especially views. This will undoubtedly change in the future. But the point is moot, because they are not really supported the is no other option for now other than https://github.com/ericniebler/range-v3.
-
C++20 Ranges Algorithms – 7 Non-Modifying Operations
range-v3 is a great library allowing you to bridge the gap: https://github.com/ericniebler/range-v3
-
CXXIter: A chainable c++20 LINQ-like iterator library
[range-v3](https://github.com/ericniebler/range-v3) which std::ranges was based on has the `to>()` which as far as I know is expected to get into c++23 :)
STL
-
Show HN: Logfmtxx – Header only C++23 structured logging library using logfmt
Again, they are barely functional.
MSVC chokes on many standard-defined constructs: https://github.com/microsoft/STL/issues/1694
clang does not claim to be "mostly usable" at all - most papers are not implemented: https://clang.llvm.org/cxx_status.html#cxx20
And gcc will only start ot be usable with CMake when version 14 is released - that has not happened yet.
And, as I mentioned before, IDE support is either buggy (Visual Studio) or non-existing (any other IDE/OS). So you're off to writing in a text editor and hoping your compiler works to a somewhat usable degree. Yes, at some point people should start using modules, I agree, but to advise library maintainers to ship modularized code... the tooling just isn't there yet.
I mean, the GitHub issue is Microsoft trying to ship their standard library modularized, they employ some of the most capable folks on the planet and pay them big money to get that done, while metaphorically sitting next to the Microsoft compiler devs, and they barely, barely get it done (with bugs, as they themselves mention). This is too much for most other library maintainers.
-
Cpp2 and cppfront – An experimental 'C++ syntax 2' and its first compiler
Notice that there are in practice three distinct implementations of the C++ standard library. They're all awful to read though, here's Microsoft's std::vector https://github.com/microsoft/STL/blob/main/stl/inc/vector
However you're being slightly unfair because Rust's Vec is just defined (opaquely) as a RawVec plus a length value, so let's link RawVec, https://doc.rust-lang.org/src/alloc/raw_vec.rs.html -- RawVec is the part responsible for the messy problem of how to actually implement the growable array type.
Still, the existence of three C++ libraries with slightly different (or sometimes hugely different) quality of implementation means good C++ code can't depend on much beyond what the ISO document promises, and yet it must guard against the nonsense inflicted by all three and by lacks of the larger language. In particular everything must use the reserved prefix so that it's not smashed inadvertently by a macro, and lots of weird C++ idioms that preserve performance by sacrificing clarity of implementation are needed, even where you'd ordinarily sacrifice to get the development throughput win of everybody know what's going on. For example you'll see a lot of "pair" types bought into existence which are there to squirrel away a ZST that in C++ can't exist, using the Empty Base Optimisation. In Rust the language has ZSTs so they can just write what they meant.
- C++ Specification vs Implementation
-
C++23: Removing garbage collection support
Here is Microsoft's implementation of map in the standard library. I think of myself as a competent programmer / computer scientist. I couldn't write this: https://github.com/microsoft/STL/blob/f392449fb72d1a387ac502...
-
std::condition_variable wait for (very) long time
Be careful on Windows, the MSVC STL implementation uses the system time, so it can be badly impacted by clock adjustments: https://github.com/microsoft/STL/issues/718
-
Compiler explorer: can you use C++23 std lib modules with MSVC already?
Can you provide a link? If it affects import std;, I'd like to add it to my tracking issue.
- Learn to write production quality STL like classes
-
MSVC C++23 Update
Do you have a list of the bugs you've filed and their current status, like the one I have for the STL? I saw you mentioned 3 bugs 7 months ago, 2 of which were fixed in 17.6 and the third of which was a duplicate of an active bug ("deducing this" is known to not yet work with modules, which is why we don't define the feature-test macro to claim full support).
- C++/CLI wrap of a C++ class that includes <future> in public header
-
Has Boost lost its charm?
Yep. And look at our implementation's name: https://github.com/microsoft/STL
What are some alternatives?
Boost.Asio - Asio C++ Library
EA Standard Template Library - EASTL stands for Electronic Arts Standard Template Library. It is an extensive and robust implementation that has an emphasis on high performance.
cppitertools - Implementation of python itertools and builtin iteration functions for C++17
asio - Boost.org asio module
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
robin-hood-hashing - Fast & memory efficient hashtable based on robin hood hashing for C++11/14/17/20
HCSR04 - Arduino library for HC-SR04, HC-SRF05, DYP-ME007, BLJ-ME007Y, JSN-SR04T ultrasonic ranging sensor
tracy - Frame profiler
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.
gcc
cpplinq - LINQ for C++ (cpplinq) is an extensible C++11 library of higher-order functions for range manipulation. cpplinq draws inspiration from LINQ for C#.
llvm-project - The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.