mirror of
https://github.com/salsa-rs/salsa.git
synced 2024-10-23 04:46:35 +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.
23 lines
337 B
Rust
23 lines
337 B
Rust
//! Test that a setting a field on a `#[salsa::input]`
|
|
//! overwrites and returns the old value.
|
|
|
|
use test_log::test;
|
|
|
|
#[salsa::input]
|
|
struct MyInput {
|
|
field: String,
|
|
}
|
|
|
|
#[salsa::tracked]
|
|
struct MyTracked<'db> {
|
|
field: MyInterned<'db>,
|
|
}
|
|
|
|
#[salsa::interned]
|
|
struct MyInterned<'db> {
|
|
field: String,
|
|
}
|
|
|
|
#[test]
|
|
fn execute() {}
|