Documentation #10
Documentation #10
Conversation
ADOBE_NONCRITICAL_PRECONDITION_CHECK will just use the precondition kind.
dabrahams
force-pushed
the
documentation
branch
from
da92b7b
to
a66fd79
Compare
| - `message`: an expression convertible to `const char*` pointing to a | ||
| [null-terminated](https://en.cppreference.com/w/cpp/string/byte) | ||
| message that is additionally passed to the violation handler. The | ||
| default value is the empty string, `""`. |
There was a problem hiding this comment.
Is nullptr allowed for the message? In a macro I believe we can force a string literal by using "" message.
There was a problem hiding this comment.
Does nullptr point to a null-terminated byte string? I think not.
In a macro I believe we can force a string literal by using "" message.
I don't understand what you're suggesting.
There was a problem hiding this comment.
@sean-parent I get it now. But why would we want to do that?
There was a problem hiding this comment.
By ensuring a string literal, you don't have to deal with null and lifetime if it escapes (on the down side, you can't build a message at runtime).
There was a problem hiding this comment.
It can only escape if you return or throw from your handler. Are you sure it's worth it? People can do any number of other bad things in their handlers too.
No description provided.