mirror of
https://github.com/salsa-rs/salsa.git
synced 2024-11-28 17:42:00 +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. |
||
|---|---|---|
| .. | ||
| main.rs | ||
| parallel_cancellation.rs | ||
| parallel_cycle_all_recover.rs | ||
| parallel_cycle_mid_recover.rs | ||
| parallel_cycle_none_recover.rs | ||
| parallel_cycle_one_recover.rs | ||
| setup.rs | ||
| signal.rs | ||