[RFC] Project Status (Feature-Complete), Ideas, Critique & Call for C++ Wrapper

[gooderfreed]

Hi everyone!

With the release of v1.3.0, easy_stack has reached its intended architectural vision. The core C11 implementation is now considered feature-complete, fully tested, fuzzed and benchmarked down to microarchitectural limits.

Currently, there are no remaining items in the internal backlog, and the library is in a stable, production-ready maintenance mode.

---

What's Next? (Call for Community Ideas & Contributions)

While the C core is finished, I would love to hear feedback from real-world usage across different domains (Game Dev, Embedded/RTOS, HFT, WebAssembly).

Specifically, contributions, ideas, or feedback in the following areas are very welcome:

1. C++ RAII Wrapper / PMR Integration:
   • Since C++ is not my primary focus (I am strictly a low-level C guy), I haven't implemented an official C++ wrapper myself.
   • If any C++ enthusiasts would like to contribute a clean, modern (C++17/20), zero-overhead RAII wrapper (EStackScope / auto-marker) or a std::pmr::memory_resource adapter, I would be extremely grateful, and PRs are warmly welcomed!
2. Exotic Hardware & Architecture Reports:
   • If you test easy_stack on unusual microcontrollers, DSPs, or RTOS environments (FreeRTOS, Zephyr), feel free to share your findings, benchmarks, or edge cases.
3. Package Manager Ports:
   • Manifests or port recipes for vcpkg, Conan, etc., integration.
4. General Critique & Micro-Optimizations:
   • If you spot any compiler-specific pessimization or have ideas for further cycle-squeezing, don't hesitate to share!

Feel free to drop your thoughts, benchmark results on different CPUs, or proposals below.

Cheers,
@gooderfreed

---

Complex inside. Simple outside.