Date: Mon, 20 Oct 2025 17:12:20 +0300
On Mon, 20 Oct 2025 at 16:58, Joshua Berne <berne_at_[hidden]> wrote:
> C++26 Contracts *also* let vendors provide you an option that says "don't let me link TUs when the TUs have different contract configurations" or even better options like "warn me if i link builds where the same function has been built with different contract configurations". Build configurations are outside the standard, and platforms are completely free to define when they do and don't work together, and to provide support for enforcing that rule. Nothing in C++26 Contracts prohibits this possibility.
There's nothing in Contracts that allows for it. And then
https://eel.is/c++draft/intro.compliance#general-2.1
says "hi".
> C++26 Contracts *also* let vendors provide you an option that says "don't let me link TUs when the TUs have different contract configurations" or even better options like "warn me if i link builds where the same function has been built with different contract configurations". Build configurations are outside the standard, and platforms are completely free to define when they do and don't work together, and to provide support for enforcing that rule. Nothing in C++26 Contracts prohibits this possibility.
There's nothing in Contracts that allows for it. And then
https://eel.is/c++draft/intro.compliance#general-2.1
says "hi".
Received on 2025-10-20 14:12:35