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.
32 lines
812 B
Rust
32 lines
812 B
Rust
//! Test that a `tracked` fn on a `salsa::input`
|
|
//! compiles and executes successfully.
|
|
|
|
use expect_test::expect;
|
|
use test_log::test;
|
|
|
|
#[salsa::interned]
|
|
struct InternedString<'db> {
|
|
data: String,
|
|
}
|
|
|
|
#[salsa::interned]
|
|
struct InternedPair<'db> {
|
|
data: (InternedString<'db>, InternedString<'db>),
|
|
}
|
|
|
|
#[salsa::tracked]
|
|
fn intern_stuff(db: &dyn salsa::Database) -> String {
|
|
let s1 = InternedString::new(db, "Hello, ".to_string());
|
|
let s2 = InternedString::new(db, "World, ".to_string());
|
|
let s3 = InternedPair::new(db, (s1, s2));
|
|
format!("{s3:?}")
|
|
}
|
|
|
|
#[test]
|
|
fn execute() {
|
|
let db = salsa::DatabaseImpl::new();
|
|
expect![[r#"
|
|
"InternedPair { data: (InternedString { data: \"Hello, \" }, InternedString { data: \"World, \" }) }"
|
|
"#]].assert_debug_eq(&intern_stuff(&db));
|
|
}
|