Date: Sun, 30 Apr 2023 17:19:27 +0000
[Andrew]
* If/when we ship contracts
*if* or *when*.
Those are heavy assumptions, and far into the future.
From what I see going on in SG21, my confidence of that materializing anytime soon - for all practical purposes – is in the low single digit.
-- Gaby
From: Andrew Tomazos <andrewtomazos_at_[hidden]>
Sent: Sunday, April 30, 2023 9:51 AM
To: ext_at_[hidden]
Cc: sg20_at_[hidden]; Gabriel Dos Reis <gdr_at_[hidden]>
Subject: Re: [isocpp-ext] [SG20] namespace composition
On Mon, May 1, 2023 at 2:15 AM Gabriel Dos Reis via Ext <ext_at_[hidden]<mailto:ext_at_[hidden]>> wrote:
Ideally, students should be taught practices they can deploy in production setting. While sanitizers and fuzzers have become accepted elements of the dev toolbox, they can't be deployed in production. That is part of why it is critical that we have a standard mechanism for turning bound checking on - or better yet, have bound checking on by default and have mechanism to opt out, after profiling data have shown that's what is needed.
If/when we ship contracts, aren't we going to eventually add them to the standard library to check preconditions? and bounds-checking of the standard containers would be amongst them? Isn't turning contracts on-and-off exactly that standard mechanism to turn bounds checking on-and-off? Or are we talking about bound-checking at the lower builtin-array level?
* If/when we ship contracts
*if* or *when*.
Those are heavy assumptions, and far into the future.
From what I see going on in SG21, my confidence of that materializing anytime soon - for all practical purposes – is in the low single digit.
-- Gaby
From: Andrew Tomazos <andrewtomazos_at_[hidden]>
Sent: Sunday, April 30, 2023 9:51 AM
To: ext_at_[hidden]
Cc: sg20_at_[hidden]; Gabriel Dos Reis <gdr_at_[hidden]>
Subject: Re: [isocpp-ext] [SG20] namespace composition
On Mon, May 1, 2023 at 2:15 AM Gabriel Dos Reis via Ext <ext_at_[hidden]<mailto:ext_at_[hidden]>> wrote:
Ideally, students should be taught practices they can deploy in production setting. While sanitizers and fuzzers have become accepted elements of the dev toolbox, they can't be deployed in production. That is part of why it is critical that we have a standard mechanism for turning bound checking on - or better yet, have bound checking on by default and have mechanism to opt out, after profiling data have shown that's what is needed.
If/when we ship contracts, aren't we going to eventually add them to the standard library to check preconditions? and bounds-checking of the standard containers would be amongst them? Isn't turning contracts on-and-off exactly that standard mechanism to turn bounds checking on-and-off? Or are we talking about bound-checking at the lower builtin-array level?
Received on 2023-04-30 17:19:31