The Master branch is now CLOSED for the beta release
Please do not commit or merge to the master branch The Beta RC1s will be available later today. — The release managers.
On Thu, Nov 6, 2025 at 10:30 AM Marshall Clow via Boost < boost@lists.boost.org> wrote:
Please do not commit or merge to the master branch
The Beta RC1s will be available later today.
An interesting edge case came up. In Kona, WG21 voted to rename nontype:
10. Apply the changes in P3774R1 (Rename std::nontype, and make it broadly useful) to the C++ working paper. This addresses ballot comments FR-021-218 and FR-019-210. https://open-std.org/jtc1/sc22/wg21/docs/papers/2025/p3774r1.html
Boost.Compat has nontype: https://github.com/boostorg/compat/blob/develop/include/boost/compat/nontype... Pretty please, with a cherry on top, could the author have permission to rename this type for this release, so it is aligned with the standard from the get-go? Thanks
On Nov 8, 2025, at 7:16 AM, Vinnie Falco <vinnie.falco@gmail.com> wrote:
On Thu, Nov 6, 2025 at 10:30 AM Marshall Clow via Boost <boost@lists.boost.org <mailto:boost@lists.boost.org>> wrote:
Please do not commit or merge to the master branch
The Beta RC1s will be available later today.
An interesting edge case came up. In Kona, WG21 voted to rename nontype:
10. Apply the changes in P3774R1 (Rename std::nontype, and make it broadly useful) to the C++ working paper. This addresses ballot comments FR-021-218 and FR-019-210. https://open-std.org/jtc1/sc22/wg21/docs/papers/2025/p3774r1.html
Boost.Compat has nontype: https://github.com/boostorg/compat/blob/develop/include/boost/compat/nontype...
Pretty please, with a cherry on top, could the author have permission to rename this type for this release, so it is aligned with the standard from the get-go?
I agree that this should be changed for the 1.90 release. For the 1.90 beta release? I’m less sure that this is necessary. — Marshall P.S. When was boost::nontype added?
participants (2)
-
Marshall Clow -
Vinnie Falco