mirror of
https://github.com/salsa-rs/salsa.git
synced 2024-10-23 20:59:51 +00:00
daaa78056a
Under this design, *all* databases are a `DatabaseImpl<U>`, where the `U` implements `UserData` (you can use `()` if there is none). Code would default to `&dyn salsa::Database` but if you want to give access to the userdata, you can define a custom database trait `MyDatabase: salsa::Databse` so long as you * annotate `MyDatabase` trait definition of impls of `MyDatabase` with `#[salsa::db]` * implement `MyDatabase` for `DatabaseImpl<U>` where `U` is your userdata (this could be a blanket impl, if you don't know the precise userdata type). The `tests/common/mod.rs` shows the pattern.
58 lines
1.1 KiB
Rust
58 lines
1.1 KiB
Rust
//! Test that when having nested tracked functions
|
|
//! we don't drop any values when accumulating.
|
|
|
|
mod common;
|
|
|
|
use expect_test::expect;
|
|
use salsa::{Accumulator, Database, DatabaseImpl};
|
|
use test_log::test;
|
|
|
|
#[salsa::accumulator]
|
|
struct Log(#[allow(dead_code)] String);
|
|
|
|
#[salsa::tracked]
|
|
fn push_logs(db: &dyn Database) {
|
|
push_a_logs(db);
|
|
}
|
|
|
|
#[salsa::tracked]
|
|
fn push_a_logs(db: &dyn Database) {
|
|
Log("log a".to_string()).accumulate(db);
|
|
push_b_logs(db);
|
|
}
|
|
|
|
#[salsa::tracked]
|
|
fn push_b_logs(db: &dyn Database) {
|
|
// No logs
|
|
push_c_logs(db);
|
|
}
|
|
|
|
#[salsa::tracked]
|
|
fn push_c_logs(db: &dyn Database) {
|
|
// No logs
|
|
push_d_logs(db);
|
|
}
|
|
|
|
#[salsa::tracked]
|
|
fn push_d_logs(db: &dyn Database) {
|
|
Log("log d".to_string()).accumulate(db);
|
|
}
|
|
|
|
#[test]
|
|
fn accumulate_chain() {
|
|
DatabaseImpl::new().attach(|db| {
|
|
let logs = push_logs::accumulated::<Log>(db);
|
|
// Check that we get all the logs.
|
|
expect![[r#"
|
|
[
|
|
Log(
|
|
"log a",
|
|
),
|
|
Log(
|
|
"log d",
|
|
),
|
|
]"#]]
|
|
.assert_eq(&format!("{:#?}", logs));
|
|
})
|
|
}
|