boost::int128 review starts today (July 22 - July 31)

Announced officially on the [Boost mailing list](https://lists.boost.org/archives/list/[email protected]/thread/GLZALH3WRHSICP6ZYOFDOPWUQTJUKOM5/)

**Introduction**

The formal review of Matt Borland's `boost::int128` for inclusion in the Boost libraries, starts today.

Int128 is a portable C++14 implementation of signed and unsigned 128-bit integers. It has no dependencies, is header-only, and can be consumed as a module in C++20. It serves as a practical solution to the partial (resp. absent) support of 128-bit integers by gcc/clang (resp. msvc), and as a lightweight alternative to heavier projects.

You can find the library and its documentation here:
\- [https://github.com/cppalliance/int128/tree/boost\_review](https://github.com/cppalliance/int128/tree/boost_review)
\- [https://develop.int128.cpp.al/overview.html](https://develop.int128.cpp.al/overview.html)
\- Compiler Explorer: [https://godbolt.org/z/5aM6K9b4r](https://godbolt.org/z/5aM6K9b4r)

Although possibly not faithful to Matt's implementation, this CE link will be handy if you are in a rush but want to play with the library.

Anyone is welcome to post a review and/or take part in subsequent discussions in the mailing list.

**Review guidelines**

Please provide feedback on the following general topics:

* What is your evaluation of the design?
* What is your evaluation of the implementation?
* What is your evaluation of the documentation?
* What is your evaluation of the potential usefulness of the library?
* Did you try to use the library? With which compiler(s)? Did you have any problems?
* How much effort did you put into your evaluation? A glance? A quick reading? In-depth study?
* Are you knowledgeable about the problem domain?

Ensure to explicitly include with your review: ACCEPT, REJECT, or CONDITIONAL ACCEPT (with acceptance conditions).

Thank you for your time making our OSS ecosystem better. Happy to start the discussions!

Arnaud Becheler (Review Manager)

https://redd.it/1v3duby
@r_cpp

I implemented Smart Pointers from scratch in C++ (UniquePtr, SharedPtr & WeakPtr)

I’ve been trying to spend more time building things from scratch instead of just reading about them.
My latest project was implementing UniquePtr, SharedPtr, and WeakPtr in C++ with reference counting.
It ended up being much more interesting than I expected. Small mistakes in reference counting quickly turned into bugs like memory leaks, double-free, and use-after-free, which made me appreciate the standard library implementation even more.
Current status:
UniquePtr
SharedPtr
WeakPtr
Reference counting
18/18 test cases passing
Repository:
https://github.com/574-jayeshSh/smart-pointer-library
I’d love to hear feedback from people who’ve implemented something similar or suggestions on what I should improve next.

https://redd.it/1v3m5k5
@r_cpp

Pure Virtual C++ Videos Are Now Available
https://devblogs.microsoft.com/cppblog/pure-virtual-c-2026-is-a-wrap/

https://redd.it/1v3myfh
@r_cpp

Project A backend-agnostic C++17 document intelligence pipeline with measurable OCR, layout and table stages

I have been working on an early-stage open-source document intelligence engine in C++17.



The goal is not to own every OCR or layout model. The core keeps typed pipeline boundaries and normalizes PDF text, OCR, layout blocks, tables, reading order, coordinates, confidence and provenance into a stable document model.



Current components include:



\- PDFium rendering and native text

\- PaddleOCR ONNX and optional Tesseract

\- RF-DETR DocLayNet and Paddle PP-DocLayoutV3

\- Table Transformer detection and structure recognition

\- JSON/Markdown/HTML output

\- small public regression datasets

\- an optional FastAPI/Redis Streams/persistent C++ Worker/React inspection platform



It is still an alpha. The current small benchmark subsets are regression checks, not production accuracy claims.



I am looking for contributors interested in C++ architecture, ONNX session reuse, OCR/CV evaluation, Redis Streams recovery, reading order, or Web-based bounding-box diagnostics.



Repository:

https://github.com/ChNanAn/technical-doc-parser

https://redd.it/1v41u7b
@r_cpp