Hi all, I'm Sayan. I am a computational thermodynamicist. I write C++ software for computing phase equilibrium : given a temperature, pressure and composition, will my liquid vapourise or not - that kinda stuff. I would like to volunteer as a maintainer of Boost.Interval (my work has good use case for the library, in searching for the global optima of free energy functions) The library has nobody looking after it right now. The listed maintainers are the original authors. I wrote to all of them in September: two addresses bounced and the third hasn't responded. Since then I've had a few PRs merged - all with the help of Lastique: mostly compilers moving or merging arithmetic across rounding-mode changes, plus functions ignoring the rounding mode, and CI. There were also some untested corners that broke containment (a big no-no for the library). I've been writing modern C++ for 3 years at this point. I don't read asm (beyond the work Matt Godbolt has done to raise the communal bar). So I'm in no sense a C++ expert, and far from the caliber of boost. I understand the maths and that's all. I use LLMs for what I can't do alone (within a reasonable amount of time), and I depend on the reviewers. What I think the library should do: 1. Never violate containment. A result not containing the true value is a bug. 2. Aspire to tightness, after that. 3. In that spirit - change any floating point setting we need to satisfy the above constraints, but keeping the user oblivious. For eg. overflow to infinity is correct behaviour for us, so it must not trap in user code. On the way out we restore the user's setting and clear only the flags we raised. There are disagreements among the backends today on this. I would follow standard practices (all the more important in the LLM era): a. Every fix should have a test that should fail sans the change. b. Small PRs, single concern only. c. Major changes and deprecation only after the list agrees. Longer term I'd like the library to conform to IEEE 1788.1-2017 <https://standards.ieee.org/ieee/1788.1/6074/>, the interval standard (lite - since apparently nobody wanted to implement the earlier standard) as an opt-in extension next to the existing API. Changing default Interval<T> would break existing code. For eg. sqrt([-4,-1]) throws today but as per 1788.1 should return an empty set. Although right now the focus is to close all the issues, fill the gaps in testing, modernise the library a bit. Main Question (besides point 3 above) : Would there be any objection to raising the minimum from C++03 to C++11? Only the mingw32 job on the CI builds C++03, and uBLAS, the only Boost library using Interval already has a C++11 floor. Thanks Sayan -- Sayan Samanta ScM'18 PhD'22 Postdoctoral Research Associate '22-'23 Materials Science | School of Engineering Brown University Providence, RI 02912 USA +1 (401) 699-1340 <(401)%20699-1340>