salsa/components/salsa-macros/Cargo.toml

[package]
name = "salsa-macros"
version = "0.18.0"
authors = ["Salsa developers"]
edition = "2021"
license = "Apache-2.0 OR MIT"
repository = "https://github.com/salsa-rs/salsa"
description = "Procedural macros for the salsa crate"

[lib]
proc-macro = true

[dependencies]
heck = "0.5.0"
proc-macro2 = "1.0"
quote = "1.0"
syn = { version = "2.0.64", features = ["full", "visit-mut"] }
synstructure = "0.13.1"
entity-based salsa preview 2022-08-01 05:32:47 +00:00			`[package]`
Rename `salsa-2022` to `salsa` 2024-06-18 07:40:21 +00:00			`name = "salsa-macros"`
			`version = "0.18.0"`
			`authors = ["Salsa developers"]`
entity-based salsa preview 2022-08-01 05:32:47 +00:00			`edition = "2021"`
Rename `salsa-2022` to `salsa` 2024-06-18 07:40:21 +00:00			`license = "Apache-2.0 OR MIT"`
			`repository = "https://github.com/salsa-rs/salsa"`
			`description = "Procedural macros for the salsa crate"`
entity-based salsa preview 2022-08-01 05:32:47 +00:00
			`[lib]`
			`proc-macro = true`

			`[dependencies]`
WIP 2024-07-11 11:30:26 +00:00			`heck = "0.5.0"`
entity-based salsa preview 2022-08-01 05:32:47 +00:00			`proc-macro2 = "1.0"`
			`quote = "1.0"`
Add missing `syn` feature requirement With the latest commit (283ccda), any project that uses Salsa hits tons of internal errors within Salsa. That's because Salsa needs syn's `full` feature, which was removed from the Cargo.toml as part of the Salsa 3.0 mega-PR. Because Salsa 1.0 still has the `full` feature in its Cargo.toml, Cargo implicitly still enables `full` for Salsa 2022, and thus the Salsa 2022 example projects compile fine -- even though any external code using Salsa does not. 2024-06-17 20:36:37 +00:00			`syn = { version = "2.0.64", features = ["full", "visit-mut"] }`
add a derive for salsa::Update And a test for it. This is required if you want to have structures in your tracked structs. Looks we need one for salsa::DebugWithDb, too. 2024-05-20 11:28:28 +00:00			`synstructure = "0.13.1"`