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.
25 lines
339 B
Rust
25 lines
339 B
Rust
//! Test that tracked structs with lifetimes not named `'db`
|
|
//! compile successfully.
|
|
|
|
mod common;
|
|
|
|
use test_log::test;
|
|
|
|
#[salsa::input]
|
|
struct MyInput {
|
|
field: u32,
|
|
}
|
|
|
|
#[salsa::tracked]
|
|
struct MyTracked1<'db1> {
|
|
field: MyTracked2<'db1>,
|
|
}
|
|
|
|
#[salsa::tracked]
|
|
struct MyTracked2<'db2> {
|
|
field: u32,
|
|
}
|
|
|
|
#[test]
|
|
fn create_db() {}
|