Files
zeekay 6a0a3ab088 Every crate names its dependencies itself, and every published crate moves a patch
No crate inherits from the workspace any longer: each manifest holds its
own version, package fields, lints and dependency specs, siblings as a
path and the exact version they publish at. The root keeps members,
exclude, resolver and profiles. Every publishable crate takes a patch
bump so the registry carries manifests that stand alone.

Claude-Session: https://claude.ai/code/session_01JupC8d38f9Lkfz62hvjG2q
2026-10-06 14:44:26 -07:00

20 lines
569 B
TOML

# Excluded from the repo workspace, so it is its own root: without this cargo walks up
# past the repo and adopts whatever workspace sits above it.
[workspace]
[package]
name = "hanzo-kernel-macros"
version = "0.1.3"
edition = "2021"
description = "The #[kernel(targets(...))] attribute for hanzo-kernel: one Rust fn, declared backends, scoped intrinsic islands."
license = "MIT OR Apache-2.0"
repository = "https://github.com/hanzoai/ml"
[lib]
proc-macro = true
[dependencies]
proc-macro2 = "1"
quote = "1"
syn = { version = "2", features = ["full", "visit-mut"] }