salsa/tests/tracked_method.rs
Niko Matsakis daaa78056a switch to new database design
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.
2024-07-28 12:47:50 +00:00

42 lines
967 B
Rust

//! Test that a `tracked` fn on a `salsa::input`
//! compiles and executes successfully.
#![allow(warnings)]
trait TrackedTrait {
fn tracked_trait_fn(self, db: &dyn salsa::Database) -> u32;
}
#[salsa::input]
struct MyInput {
field: u32,
}
#[salsa::tracked]
impl MyInput {
#[salsa::tracked]
fn tracked_fn(self, db: &dyn salsa::Database) -> u32 {
self.field(db) * 2
}
#[salsa::tracked(return_ref)]
fn tracked_fn_ref(self, db: &dyn salsa::Database) -> u32 {
self.field(db) * 3
}
}
#[salsa::tracked]
impl TrackedTrait for MyInput {
#[salsa::tracked]
fn tracked_trait_fn(self, db: &dyn salsa::Database) -> u32 {
self.field(db) * 4
}
}
#[test]
fn execute() {
let mut db = salsa::DatabaseImpl::new();
let object = MyInput::new(&mut db, 22);
// assert_eq!(object.tracked_fn(&db), 44);
// assert_eq!(*object.tracked_fn_ref(&db), 66);
assert_eq!(object.tracked_trait_fn(&db), 88);
}