82f07fe6d1
This is following `hashbrown`'s switch in v0.15 from ahash to foldhash for its `default-haster` feature, applied only to helix-event for now. I don't have a strong preference between the two. Benchmarks in Spellbook, which is particularly sensitive to hashers and hash table performance, show no perceptible difference. Foldhash is dependency-free though. Once we migrate to the new tree-sitter bindings and highlighter we should be able to eliminate the remaining dependencies on ahash.
29 lines
931 B
TOML
29 lines
931 B
TOML
[package]
|
|
name = "helix-event"
|
|
version.workspace = true
|
|
authors.workspace = true
|
|
edition.workspace = true
|
|
license.workspace = true
|
|
rust-version.workspace = true
|
|
categories.workspace = true
|
|
repository.workspace = true
|
|
homepage.workspace = true
|
|
|
|
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
|
|
|
|
[dependencies]
|
|
foldhash.workspace = true
|
|
hashbrown = "0.15"
|
|
tokio = { version = "1", features = ["rt", "rt-multi-thread", "time", "sync", "parking_lot", "macros"] }
|
|
# the event registry is essentially read only but must be an rwlock so we can
|
|
# setup new events on initialization, hardware-lock-elision hugely benefits this case
|
|
# as it essentially makes the lock entirely free as long as there is no writes
|
|
parking_lot = { version = "0.12", features = ["hardware-lock-elision"] }
|
|
once_cell = "1.20"
|
|
|
|
anyhow = "1"
|
|
log = "0.4"
|
|
futures-executor = "0.3.31"
|
|
|
|
[features]
|
|
integration_test = []
|