This one’s best done after migrating to the community project so we can have the correct url
Will probably want to either convert the solutions files to markdown with katla or manually, and add them in a an appendex. Will need to go back and insert links/references.
Get an admonishment extension up and running and edit to use it as appropiate
Need to:
- Remove use of first person singular, to reflect the collective ownership
- Update prose to reflect the new sub-chapter structure
- Update links and clean up broken ones
- Other minor editing changes to make the text flow better
Like the wiki library page
Make sure section names match up with headers in solutions
Thread local IDEMode?
Should golden test the repl outputs to detect breakage
These should also be compared in a whitespace insensitive way, im thinking, like:
```repl-session
> length ["lines that start with > are repl commands"]
1
> length ["subsequent lines before the next", "are the golden output"]
2
```This keeps it readable as a raw markdown document, but provides easy processing for extraction and injection of the actual repl output complete with highlighting.
Because I love myself
When a subchapter reimplements a standard library type, we should maybe call this out and use the standard library type in future subchapters to decrease cross dependencies
Could also potentially insert automatic linking?
This needs to come early in the book so new programmers can make sense of the use of imports to reference statements from the previous chapter.
Particularly in the context of record constructors