mirror of
https://github.com/BLAKE3-team/BLAKE3
synced 2024-05-21 02:46:06 +02:00
cb32f0bd14
New methods: - update_reader - update_mmap - update_mmap_rayon These are more discoverable, more convenient, and safer. There are two problems I want to avoid by taking a `Path` instead of a `File`. First, exposing `Mmap` objects to the caller is fundamentally unsafe, and making `maybe_mmap_file` private avoids that issue. Second, taking a `File` raises questions about whether memory mapped reads should behave like regular file reads. (Should they respect the current seek position? Should they update the seek position?) Taking a `Path` from the caller and opening the `File` internally avoids these questions.
28 lines
687 B
INI
28 lines
687 B
INI
[package]
|
|
name = "b3sum"
|
|
version = "1.4.1"
|
|
authors = ["Jack O'Connor <oconnor663@gmail.com>"]
|
|
description = "a command line implementation of the BLAKE3 hash function"
|
|
repository = "https://github.com/BLAKE3-team/BLAKE3"
|
|
license = "CC0-1.0 OR Apache-2.0"
|
|
readme = "README.md"
|
|
edition = "2021"
|
|
|
|
[features]
|
|
neon = ["blake3/neon"]
|
|
prefer_intrinsics = ["blake3/prefer_intrinsics"]
|
|
pure = ["blake3/pure"]
|
|
|
|
[dependencies]
|
|
anyhow = "1.0.25"
|
|
blake3 = { version = "1", path = "..", features = ["mmap", "rayon"] }
|
|
clap = { version = "4.0.8", features = ["derive", "wrap_help"] }
|
|
hex = "0.4.0"
|
|
memmap2 = "0.7.0"
|
|
rayon = "1.2.1"
|
|
wild = "2.0.3"
|
|
|
|
[dev-dependencies]
|
|
duct = "0.13.3"
|
|
tempfile = "3.1.0"
|