react-native-quick-crypto 1.0.19 → 1.1.1

package/deps/blake3/src/io.rs

@@ -1,64 +0,0 @@
-//! Helper functions for efficient IO.
-
-#[cfg(feature = "std")]
-pub(crate) fn copy_wide(
-    mut reader: impl std::io::Read,
-    hasher: &mut crate::Hasher,
-) -> std::io::Result<u64> {
-    let mut buffer = [0; 65536];
-    let mut total = 0;
-    loop {
-        match reader.read(&mut buffer) {
-            Ok(0) => return Ok(total),
-            Ok(n) => {
-                hasher.update(&buffer[..n]);
-                total += n as u64;
-            }
-            // see test_update_reader_interrupted
-            Err(e) if e.kind() == std::io::ErrorKind::Interrupted => continue,
-            Err(e) => return Err(e),
-        }
-    }
-}
-
-// Mmap a file, if it looks like a good idea. Return None in cases where we know mmap will fail, or
-// if the file is short enough that mmapping isn't worth it. However, if we do try to mmap and it
-// fails, return the error.
-//
-// SAFETY: Mmaps are fundamentally unsafe, because you can call invariant-checking functions like
-// str::from_utf8 on them and then have them change out from under you. Letting a safe caller get
-// their hands on an mmap, or even a &[u8] that's backed by an mmap, is unsound. However, because
-// this function is crate-private, we can guarantee that all can ever happen in the event of a race
-// condition is that we either hash nonsense bytes or crash with SIGBUS or similar, neither of
-// which should risk memory corruption in a safe caller.
-//
-// PARANOIA: But a data race...is a data race...is a data race...right? Even if we know that no
-// platform in the "real world" is ever going to do anything other than compute the "wrong answer"
-// if we race on this mmap while we hash it, aren't we still supposed to feel bad about doing this?
-// Well, maybe. This is IO, and IO gets special carve-outs in the memory model. Consider a
-// memory-mapped register that returns random 32-bit words. (This is actually realistic if you have
-// a hardware RNG.) It's probably sound to construct a *const i32 pointing to that register and do
-// some raw pointer reads from it. Those reads should be volatile if you don't want the compiler to
-// coalesce them, but either way the compiler isn't allowed to just _go nuts_ and insert
-// should-never-happen branches to wipe your hard drive if two adjacent reads happen to give
-// different values. As far as I'm aware, there's no such thing as a read that's allowed if it's
-// volatile but prohibited if it's not (unlike atomics). As mentioned above, it's not ok to
-// construct a safe &i32 to the register if you're going to leak that reference to unknown callers.
-// But if you "know what you're doing," I don't think *const i32 and &i32 are fundamentally
-// different here. Feedback needed.
-#[cfg(feature = "mmap")]
-pub(crate) fn maybe_mmap_file(file: &std::fs::File) -> std::io::Result<Option<memmap2::Mmap>> {
-    let metadata = file.metadata()?;
-    let file_size = metadata.len();
-    if !metadata.is_file() {
-        // Not a real file.
-        Ok(None)
-    } else if file_size < 16 * 1024 {
-        // Mapping small files is not worth it, and some special files that can't be mapped report
-        // a size of zero.
-        Ok(None)
-    } else {
-        let map = unsafe { memmap2::Mmap::map(file)? };
-        Ok(Some(map))
-    }
-}

package/deps/blake3/src/join.rs

@@ -1,92 +0,0 @@
-//! The multi-threading abstractions used by `Hasher::update_with_join`.
-//!
-//! Different implementations of the `Join` trait determine whether
-//! `Hasher::update_with_join` performs multi-threading on sufficiently large
-//! inputs. The `SerialJoin` implementation is single-threaded, and the
-//! `RayonJoin` implementation (gated by the `rayon` feature) is multi-threaded.
-//! Interfaces other than `Hasher::update_with_join`, like [`hash`](crate::hash)
-//! and [`Hasher::update`](crate::Hasher::update), always use `SerialJoin`
-//! internally.
-//!
-//! The `Join` trait is an almost exact copy of the [`rayon::join`] API, and
-//! `RayonJoin` is the only non-trivial implementation. Previously this trait
-//! was public, but currently it's been re-privatized, as it's both 1) of no
-//! value to most callers and 2) a pretty big implementation detail to commit
-//! to.
-//!
-//! [`rayon::join`]: https://docs.rs/rayon/1.3.0/rayon/fn.join.html
-
-/// The trait that abstracts over single-threaded and multi-threaded recursion.
-///
-/// See the [`join` module docs](index.html) for more details.
-pub trait Join {
-    fn join<A, B, RA, RB>(oper_a: A, oper_b: B) -> (RA, RB)
-    where
-        A: FnOnce() -> RA + Send,
-        B: FnOnce() -> RB + Send,
-        RA: Send,
-        RB: Send;
-}
-
-/// The trivial, serial implementation of `Join`. The left and right sides are
-/// executed one after the other, on the calling thread. The standalone hashing
-/// functions and the `Hasher::update` method use this implementation
-/// internally.
-///
-/// See the [`join` module docs](index.html) for more details.
-pub enum SerialJoin {}
-
-impl Join for SerialJoin {
-    #[inline]
-    fn join<A, B, RA, RB>(oper_a: A, oper_b: B) -> (RA, RB)
-    where
-        A: FnOnce() -> RA + Send,
-        B: FnOnce() -> RB + Send,
-        RA: Send,
-        RB: Send,
-    {
-        (oper_a(), oper_b())
-    }
-}
-
-/// The Rayon-based implementation of `Join`. The left and right sides are
-/// executed on the Rayon thread pool, potentially in parallel. This
-/// implementation is gated by the `rayon` feature, which is off by default.
-///
-/// See the [`join` module docs](index.html) for more details.
-#[cfg(feature = "rayon")]
-pub enum RayonJoin {}
-
-#[cfg(feature = "rayon")]
-impl Join for RayonJoin {
-    #[inline]
-    fn join<A, B, RA, RB>(oper_a: A, oper_b: B) -> (RA, RB)
-    where
-        A: FnOnce() -> RA + Send,
-        B: FnOnce() -> RB + Send,
-        RA: Send,
-        RB: Send,
-    {
-        rayon_core::join(oper_a, oper_b)
-    }
-}
-
-#[cfg(test)]
-mod test {
-    use super::*;
-
-    #[test]
-    fn test_serial_join() {
-        let oper_a = || 1 + 1;
-        let oper_b = || 2 + 2;
-        assert_eq!((2, 4), SerialJoin::join(oper_a, oper_b));
-    }
-
-    #[test]
-    #[cfg(feature = "rayon")]
-    fn test_rayon_join() {
-        let oper_a = || 1 + 1;
-        let oper_b = || 2 + 2;
-        assert_eq!((2, 4), RayonJoin::join(oper_a, oper_b));
-    }
-}