-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make <*const T>::is_null
const fn
#74940
Conversation
This comment has been minimized.
This comment has been minimized.
r=me with the last nits fixed and after squashing |
☔ The latest upstream changes (presumably #75383) made this pull request unmergeable. Please resolve the merge conflicts. |
@bors r=RalfJung |
📌 Commit 34c3c0d has been approved by |
@@ -0,0 +1,16 @@ | |||
// compile-flags: --crate-type=lib | |||
// check-pass |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure check-pass
is enough for this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
considering that it did cause stderr output when I had the asserts inverted, yes.
These constants are evaluated by the lint that used to be const_err
, and check
runs all lints.
⌛ Testing commit 34c3c0d with merge 6495955293bc979b4b521db8cb744f36bba1fd6f... |
💔 Test failed - checks-actions |
@oli-obk
|
@bors r=RalfJung |
📌 Commit daf7a37 has been approved by |
☀️ Test successful - checks-actions, checks-azure |
r? @RalfJung
cc @rust-lang/wg-const-eval
tracking issue: #74939