Update timespec comments to say "nanoseconds" #3182
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! I've pushed this commit to the incoming branch. It will show up on master sometime this week. |
RalfJung
pushed a commit
to RalfJung/rust
that referenced
this pull request
Nov 25, 2023
RalfJung
pushed a commit
to RalfJung/rust
that referenced
this pull request
Nov 25, 2023
jaisnan
pushed a commit
to jaisnan/rust-dev
that referenced
this pull request
Jul 29, 2024
typed_swap needs to be a no-op on ZSTs as pointers to those have an arbitrary value in Kani. Resolves: rust-lang#3182
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
timespec uses nanoseconds, but its comments still refer to (timeval's) microseconds.