hifitime
time
| hifitime | time | |
|---|---|---|
| 2 | 12 | |
| 297 | 1,011 | |
| 0.7% | 2.0% | |
| 9.0 | 8.7 | |
| 6 days ago | 10 days ago | |
| Rust | Rust | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
hifitime
-
Is there something like "super-safe" rust?
kani (e.g. used by hifitime)
-
Hifitime 3.5.0: time.rs and chrono alternative, only more precise, formally verified, and used in scientific and engineering programs
I could add that to the documentation. There's a benchmark test here: https://github.com/nyx-space/hifitime/actions/runs/3257976296.
time
-
Rust: Actix-web and Daily Logging
// To load RUST_LOG from .env file. dotenv().ok(); /* On Ubuntu 22.10, calling UtcOffset's offset methods causes IndeterminateOffset error!! See also https://github.com/time-rs/time/pull/297 ... */ // TO_DO: 11 is the current number of hours the Australian Eastern Standard Time (AEST) // is ahead of UTC. This value need to be worked out dynamically -- if it is at all // possible on Linux!! // let guard = init_app_logger(UtcOffset::from_hms(11, 0, 0).unwrap());
-
Getaddrinfo() on glibc calls getenv(), oh boy
The problem is that this effects higher languages too, because they often build on libc. And on some OSes, they don't have a choice, because the system call interface is unstable and/or undocumented).
For example in rust, multiple time libraries were found to be unsound if `std::env::set_env` was ever called from a multi-threaded program. See:
https://github.com/time-rs/time/issues/293 and https://github.com/chronotope/chrono/issues/499
https://github.com/rust-lang/rust/issues/27970
https://github.com/rust-lang/rust/issues/90308
- The time crate has officially adopted an N-2 MSRV policy for end-user improvements and an N-4 MSRV policy for internal improvements.
-
Simple, fast and safety alternative for unzip
On that note, it would also be good to configure cargo-deny so that a CI pipeline and any maintainer can easily audit the current dependency versions. Sometimes CVEs require a new major semver (looking at you, time 0.1.x and thus chrono 0.4.x), so it's not enough to rely on people installing the tool with semver-compatible updates. Automatically auditing dependencies is really important, and given how easy cargo-deny makes it, I don't think many projects have any excuse not to configure it.
- time: MSRV policy is changing beginning 2023-07-01 to N-2 rustc versions
-
Hifitime 3.5.0: time.rs and chrono alternative, only more precise, formally verified, and used in scientific and engineering programs
I've come to understand that correct support for leap seconds for time computations cannot be implemented in a reliable and globally consistent manner. Here is a GitHub discussion that touches on this.
-
What's new in SeaORM 0.9.0
Upgrade time to 0.3
-
What lightweight date/time library to use? [2022 edition]
I'm not fully aware of all the history but here's what I think happened: time 0.1 was originally a minimal wrapper around libc time functions, maintained by Alex Crichton. (I seem to remember it may have been part of the std library before 1.0, but I'm not sure about that part.) In August of 2016 it was declared to no longer be actively maintained, with the README stating bugs would still get fixed.
- What should we do about CVE-2020-26235 (localtime_r may be unsound)?
-
no_std with Error trait?
link to source code
What are some alternatives?
tai - tai (Terminal Ascii Images) tool to convert images to text written in Rust
chrono - Date and time library for Rust
rustig - A tool to detect code paths leading to Rust's panic handler
bitvec - A crate for managing memory bit by bit
kani - Kani Rust Verifier
bitsvec - A bit vector with the Rust standard library's portable SIMD API.
prusti-dev - A static verifier for Rust, based on the Viper verification infrastructure.
wyhash-rs - wyhash fast portable non-cryptographic hashing algorithm and random number generator in Rust
no-panic - Attribute macro to require that the compiler prove a function can't ever panic
uuid - Generate and parse UUIDs.
MIRAI - Rust mid-level IR Abstract Interpreter
binfarce - Extremely minimal parser for ELF/PE/Mach-o/ar