proxy
AnyAny
proxy | AnyAny | |
---|---|---|
3 | 22 | |
1,202 | 423 | |
29.3% | - | |
7.5 | 6.2 | |
11 days ago | 28 days ago | |
C++ | C++ | |
MIT License | Apache License 2.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.
proxy
-
Static Interfaces, concepts vs de-virtualisation?
Proxy seems more likely than Dyno or AnyAny to be a standard way of doing this in C++'s future.
-
C++ Polymorphism Without Inheritance Using Glaze
https://github.com/microsoft/proxy Implementation submitted for standarization
-
Runtime Concept Idiom: Opinions
So basically you have to undo the type erasure? I think I'm going to try the proxy library found here. https://github.com/microsoft/proxy
AnyAny
- DynaMix 2.0.0 Released
-
rust-like traits on plain C++ with short macro (type erasure actually)
https://github.com/kelbon/AnyAny trait(add, void(int), self.add(args...));
-
Static Interfaces, concepts vs de-virtualisation?
i dont know what he means, but with this type erasure library you can have non virtual interface and still use dynamic polymorphism with those types, so you dont need choose *do i need to do this type polymorphic* etc
-
[C++23] constexpr std::function in 40 LOC (simplified) powered by constexpr std::unique_ptr
There are also invoking from tuple and curring (just an example of technique)https://github.com/kelbon/AnyAny/blob/main/examples/functional_paradigm.hpp
-
A call to action: Think seriously about “safety”; then do something sensible about it -> Bjarne Stroustrup
As for my example containers: https://github.com/kelbon/AnyAny/blob/main/include/data_parallel_vector.hpp
- C++ Polymorphism Without Inheritance Using Glaze
-
С++20 library for high-performance polymorphic types usage
variant_swarm - container which behaves as set of std::variant, but with much faster visit operation and operation for getting view to all values of type T. It short, it just stores all types separatelly and supports operations visit, view, also you can change underlying containers for Ts..., it is std::vector by default https://github.com/kelbon/AnyAny/blob/main/include/variant_swarm.hpp
-
I wrote multidispatching(runtime overload resolution) in C++ (and its not std::variant)
Its part of my library for working with polymorphic types.
-
I wrote a library that emulates dyn traits from Rust in C++
Good idea selling Rust from behind enemy lines soldier! My god, your readme doesn't even mention Rust, wonderful!
-
Using final in C++ to improve performance
https://github.com/kelbon/AnyAny here you can see how it implemented, for example
What are some alternatives?
iface - Anonymous, non-intrusive interfaces in C++
tolc - A bindings compiler for C++
Aggreget - Use your structures like tuples. Similar to MagicGet but using C++ 20 concepts.
dyno - Runtime polymorphism done right
kumi - C++20 Compact Tuple Tools
Kalman - Kalman Filter
glfwpp - GLFW C++ Wrapper - thin, modern, C++17, header-only GLFW wrapper
tinyformat - Minimal, type safe printf replacement library for C++
glaze - Extremely fast, in memory, JSON and interface library for modern C++
kelcoro - C++20 coroutine library
polytail - Rust-like trait-based polymorphism for C++
ReactivePlusPlus - Implementation of async observable/observer (Reactive Programming) in C++ with care about performance and templates in mind in ReactiveX approach