mirror of
https://github.com/salsa-rs/salsa.git
synced 2024-11-24 12:16:25 +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.
16 lines
372 B
Rust
16 lines
372 B
Rust
//! Test that creating a tracked struct outside of a
|
|
//! tracked function panics with an assert message.
|
|
|
|
#[salsa::tracked]
|
|
struct MyTracked<'db> {
|
|
field: u32,
|
|
}
|
|
|
|
#[test]
|
|
#[should_panic(
|
|
expected = "cannot create a tracked struct disambiguator outside of a tracked function"
|
|
)]
|
|
fn execute() {
|
|
let db = salsa::DatabaseImpl::new();
|
|
MyTracked::new(&db, 0);
|
|
}
|