zyntax/Cargo.toml at main · zyntax-project/zyntax · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
[workspace]
resolver = "2"
members = [
    "crates/typed_ast",
    "crates/compiler",
    "crates/zyntax_cli",
    "crates/runtime",
    "crates/zyntax_plugin_macros",
    "crates/zyn_peg",
    "crates/zyntax_embed",
    "crates/zyntax_wasm",
    "crates/zynml",
    "crates/pattern_engine",
    "crates/zyntax_python",
    "crates/zyntax_ts",
    "crates/zyntax_lua",
    "crates/zyntax_lua/capi",
    "crates/zyntax_builtins",
    "crates/zyntax_plugin_tables",
    "crates/passes/normalization",
    "crates/passes/algebraic_effects",
    "crates/passes/krio_adapter",
    "sdk/zrtl",
    "sdk/zrtl_macros",
    "sdk/zrtl_native",
    "examples/imagepipe",
]


# full_moon with empty statements accepted; see vendor/full_moon/Cargo.toml.
[patch.crates-io]
full_moon = { path = "vendor/full_moon" }

[workspace.dependencies]
rayon = "1.10.0"
dashmap = "6.1.0"
crossbeam = "0.8.4"
parking_lot = "0.12.3"
thiserror = "2.0.11"
serde_json = "1.0.138"
serde = {version= "1.0.217", features = ["derive", "rc"]}
tempfile = "3.16.0"
colored = "3.0.0"
lazy_static = "1.5.0"
regex = "1.11.1"
# `js` enables web-sys-backed randomness on wasm32-unknown-unknown.
# It's a no-op on native targets; safe to set unconditionally.
uuid = { version = "1.10.0", features = ["v4", "serde", "js"] }
miette = "7.2.0"
typed-arena = "2.0.2"
string-interner = "0.17.0"
ariadne = "0.5"

[workspace.lints.rust]
warnings = "allow"
# `zrtl_plugin!` gates its dlopen exports on this feature of the crate
# that expands it, whether or not that crate declares it.
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(feature, values("linked-into-host"))'] }

[workspace.lints.clippy]
all = "allow"

# Debug builds keep line tables and drop the rest of the DWARF.
#
# Backtraces still name a file and a line, which is what they are read
# for; stepping in a debugger and inspecting locals is what goes. On
# macOS the default `split-debuginfo = "unpacked"` leaves one object file
# per codegen unit beside each binary, and the executable's debug map
# points into them, so cargo cannot remove them when a crate is rebuilt
# under a new hash. Every rebuild leaves a full set behind, and the
# volume of each set is set here.
[profile.dev]
debug = "line-tables-only"