Skip to content

docs: repoint the links the repository split broke #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sajonaro merged 1 commit into from
Aug 14, 2026
Merged

docs: repoint the links the repository split broke #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion jobshop-best/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,7 @@ There is no guard stopping it at t9 and none is needed: **where the chain has
no answer the move is absent** — not a no-op, which would be a self-loop and
would stop the situation ever being reported as a dead end. The full argument,
including the swap that fixes when the right-hand side is read, is
[`docs/set-as-chain.md`](../../../docs/set-as-chain.md).
[`docs/kernel-spec.md` §10.3](https://github.com/writ-lang/writ/blob/main/docs/kernel-spec.md).

The space is unchanged: still 1314 situations, still an optimum of five.

Expand Down
2 changes: 1 addition & 1 deletion jobshop-possible/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ Now nobody can move. `a` waits on `b`, `b` waits on `c`, `c` waits on `a`. No
job will ever release a machine, because releasing requires first acquiring the
next one. The shop is stopped **forever**, and no amount of waiting fixes it.

![The deadlock: each job holds one machine and waits for the next, in a cycle](../../../docs/diagrams/jobshop-deadlock.svg)
![The deadlock: each job holds one machine and waits for the next, in a cycle](https://github.com/writ-lang/writ/blob/main/docs/diagrams/jobshop-deadlock.svg)

Solid is *holds*, dashed is *waited for*. Follow either kind of arrow all the
way round and you return where you started — that cycle **is** the deadlock.
Expand Down
4 changes: 2 additions & 2 deletions libraries/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ forms — never a model's own choice of what to run.
not be redeclared (kernel §7), so every model loading `chess.lib.writ` gives up
`board`, `square`, `queen`, `free`, `empty` and the entity names. That cost is
exactly why these are **domain** libraries and not additions to
[`core/stdlib/stdlib.writ`](../../../core/stdlib/stdlib.writ): the standard
[`core/stdlib/stdlib.writ`](https://github.com/writ-lang/writ/blob/main/core/stdlib/stdlib.writ): the standard
library may not spend the shared namespace on a worldly concept. It is also the
difference in kind — `stdlib.writ` is shipped and installed; these are not.

Expand Down Expand Up @@ -69,7 +69,7 @@ writ: resolved "stdlib.writ" -> core/stdlib/stdlib.writ

## A third one, deliberately not here

[`tests/models/politics.lib.writ`](../../models/politics.lib.writ) is a domain
[`tests/models/politics.lib.writ`](https://github.com/writ-lang/writ/blob/main/tests/models/politics.lib.writ) is a domain
library too, and it stays with the unit-test corpus it serves. Moving it would
couple the unit tests to the examples tree for no gain — a library belongs
wherever all of its models can see it, and for that one, that is `tests/models/`.
Loading