blue-lang-syntax 0.0.21

blue's surface syntax: lexer, parser, and lowering to the tatara-lisp quoted form.
Documentation 
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

[package]
name = "blue-lang-syntax"
description = "blue's surface syntax: lexer, parser, and lowering to the tatara-lisp quoted form."
version.workspace = true
edition.workspace = true
rust-version.workspace = true
authors.workspace = true
license.workspace = true
repository.workspace = true

[dependencies]
tatara-lisp = { workspace = true }

[dev-dependencies]
# Property-based totality. The corpus suites prove the parser survives THESE
# inputs; proptest widens that to input the corpus cannot reach — random and,
# more usefully, structurally-generated near-valid programs, which is where
# real parsers break. Dev-only, so no consumer carries it.
proptest = "1"
# The cross-crate differential lives here because it is a property ABOUT the
# parser (format must preserve what parse sees).
#
# PATH ONLY, no version — see the rule in `blue-lang-runtime`'s dev-dep block.
# "Dev-only, so no cycle ships" is FALSE for a versioned dev-dep: cargo keeps a
# dev-dependency that carries a `version` in the published manifest, so it must
# resolve on the registry, and `blue-lang-fmt` depends on this crate. That is a
# registry cycle and it stalled every publish from v0.0.13 to v0.0.19.
# `workspace = true` cannot express "unversioned here" — one
# [workspace.dependencies] entry serves both dep kinds — so a sibling dev-dep
# spells its path out. `the_registry_dependency_graph_is_acyclic` is the gate.
blue-lang-fmt = { path = "../blue-lang-fmt" }
blue-lang-runtime = { path = "../blue-lang-runtime" }
tatara-lisp-eval = { workspace = true }