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
..
accumulator.rs	pacify the merciless clippy	2024-07-19 09:20:41 -04:00
db.rs	switch to new database design	2024-07-28 12:47:50 +00:00
db_lifetime.rs
debug.rs
fn_util.rs	pacify the merciless clippy	2024-07-19 09:20:41 -04:00
hygiene.rs
input.rs	cleanup getters/setters	2024-07-19 07:22:09 -04:00
interned.rs	cleanup getters/setters	2024-07-19 07:22:09 -04:00
lib.rs
options.rs
salsa_struct.rs	pacify the merciless clippy	2024-07-19 09:20:41 -04:00
tracked.rs
tracked_fn.rs	Respct no_eq attribute for tracked functions	2024-07-20 08:47:51 +02:00
tracked_impl.rs	pacify the merciless clippy	2024-07-19 09:20:41 -04:00
tracked_struct.rs	cleanup getters/setters	2024-07-19 07:22:09 -04:00
update.rs	squelch most clippy warnings in generated code	2024-07-19 10:00:03 -04:00
xform.rs