-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathcodehelion.toml
More file actions
34 lines (31 loc) · 1.44 KB
/
Copy pathcodehelion.toml
File metadata and controls
34 lines (31 loc) · 1.44 KB
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
# codehelion, configured for codehelion.
#
# Only the seam ledger is set here. Everything else stays at the built-in
# defaults, because a tool whose own repository needs the defaults tuned to be
# readable has the wrong defaults.
# The two frontends implement the same semantics against two grammars, and the
# history says so: a rule added to one has repeatedly reached the other only
# after a later fix. This entry is what makes that visible at the moment it
# happens rather than in the next audit.
[[seam]]
id = "frontend-c-cpp"
members = ["crates/codehelion-frontend-c/**", "crates/codehelion-frontend-cpp/**"]
note = "same semantics implemented twice across the two frontends"
# The two READMEs are one document written twice. Nothing enforces that an
# edit to one reaches the other, and the co-change figures say they have moved
# together for almost every change either has ever had.
[[seam]]
id = "readme-en-ja"
members = ["README.md", "README_ja.md"]
note = "one overview in two languages"
# One job per operating system: build the artifact fixtures and check what the
# reader makes of them. A rule added to the ELF script usually belongs in the
# other two, and nothing but a reader's memory says so.
[[seam]]
id = "artifact-fixture-scripts"
members = [
"scripts/verify-artifact-fixtures.sh",
"scripts/verify-macho-artifact-fixtures.sh",
"scripts/verify-pe-artifact-fixtures.ps1",
]
note = "the same fixture verification written once per platform"