salsa/tests/override_new_get_set.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

70 lines
1.4 KiB
Rust

//! Test that the `constructor` macro overrides
//! the `new` method's name and `get` and `set`
//! change the name of the getter and setter of the fields.
#![allow(warnings)]
use std::fmt::Display;
use salsa::Setter;
#[salsa::db]
trait Db: salsa::Database {}
#[salsa::input(constructor = from_string)]
struct MyInput {
#[get(text)]
#[set(set_text)]
field: String,
}
impl MyInput {
pub fn new(db: &mut dyn Db, s: impl Display) -> MyInput {
MyInput::from_string(db, s.to_string())
}
pub fn field(self, db: &dyn Db) -> String {
self.text(db)
}
pub fn set_field(self, db: &mut dyn Db, id: String) {
self.set_text(db).to(id);
}
}
#[salsa::interned(constructor = from_string)]
struct MyInterned<'db> {
#[get(text)]
#[return_ref]
field: String,
}
impl<'db> MyInterned<'db> {
pub fn new(db: &'db dyn Db, s: impl Display) -> MyInterned<'db> {
MyInterned::from_string(db, s.to_string())
}
pub fn field(self, db: &'db dyn Db) -> &str {
&self.text(db)
}
}
#[salsa::tracked(constructor = from_string)]
struct MyTracked<'db> {
#[get(text)]
field: String,
}
impl<'db> MyTracked<'db> {
pub fn new(db: &'db dyn Db, s: impl Display) -> MyTracked<'db> {
MyTracked::from_string(db, s.to_string())
}
pub fn field(self, db: &'db dyn Db) -> String {
self.text(db)
}
}
#[test]
fn execute() {
salsa::DatabaseImpl::new();
}