about summary refs log tree commit diff
path: root/tests/coverage/branch/lazy-boolean.rs
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2024-12-21 22:16:02 +0100
committerGitHub <noreply@github.com>2024-12-21 22:16:02 +0100
commit3aedae24a25ac29960a35709712e45034dff87df (patch)
treeaf84d46becb6f80fecb5b389e40b85be2ad62a8c /tests/coverage/branch/lazy-boolean.rs
parent51df98ddb094b39b2e17d24f887cd66c52560ef6 (diff)
parente6efbb210b037b7e921eac6db5ec79d3c241e2b4 (diff)
downloadrust-3aedae24a25ac29960a35709712e45034dff87df.tar.gz
rust-3aedae24a25ac29960a35709712e45034dff87df.zip
Rollup merge of #134325 - theemathas:is_null-docs, r=RalfJung
Correctly document CTFE behavior of is_null and methods that call is_null.

The "panic in const if CTFE doesn't know the answer" behavior was discussed to be the desired behavior in #74939, and is currently how the function actually behaves.

I intentionally wrote this documentation to allow for the possibility that a panic might not occur even if the pointer is out of bounds, because of #133700 and other potential changes in the future.

This is beta-nominated since `const fn is_null` stabilization is in beta already but the docs there are wrong, and it seems better to have the docs be correct at the time of stabilization.
Diffstat (limited to 'tests/coverage/branch/lazy-boolean.rs')
0 files changed, 0 insertions, 0 deletions