Pin the compiler to v0.2.9 - #41
Merged
Merged
Conversation
The playground, the diagnostics index and the install page all move together: `play.js` and `errors.js` carry the tag, the install page names the release in prose, and `tools/check.mjs` fails when any of the three disagrees. The corpus is unchanged between v0.2.8 and v0.2.9, so `examples/index.json` moves by one line. Twenty-nine examples, fourteen in the picker, one the page can start: the same answers, from a newer artifact. The artifact emits nine kinds over the corpus and `play.js` renders ten, so no line type falls through to the default arm. The install page had more to say this time, because two of the things it describes stopped being the only way to do them. `deed` is on crates.io now, as `deed-lang`, so "From source" was telling you to clone a repository to get a binary that `cargo install deed-lang` fetches. And the release carries `install.sh` and `install.ps1`, which work out the asset for the machine, refuse it if its hash is not the one the release published, and leave one file in a directory that needs no password to write. The page led with the manual unpack, which is now the long way round rather than the way. So: a "One line" section at the top, with what the hash does and does not buy stated plainly, and links to both scripts, because piping a script into a shell is a thing worth being uneasy about and the honest answer is that they are short and readable. The manual path keeps every word it had, under "By hand instead". `deed new` is on the command table, and it opens "A first program", which until now told a reader to type a module header out of a web page. The transcript is the output of the released binary: two files, three tests, and only two of them written down.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves the pin from v0.2.8 to v0.2.9, and rewrites the parts of the install
page that v0.2.9 made into the long way round.
The pin.
play.jsanderrors.jscarry the tag,install/names therelease sixteen times in prose, and
one-clause/carries the version prefix onits share links.
tools/check.mjscompares all of them and passes.The corpus did not change between the two releases, so
examples/index.jsonmoves by one line: still twenty-nine examples, fourteen in the picker, one the
page can start. Measured rather than assumed, the artifact emits nine
kindsover the whole corpus (
capability diagnostic formatted obligation output property result summary test) andplay.jshas tencasearms, so nothingfalls through to
default:and prints raw JSON.Verified in a browser against the committed artifact: the playground reports
Deed 0.2.9, runs the landing program, aone-clauseshare link opens with noversion-mismatch warning, and
errors/builds its index of 104 pages.The install page. Two of the things it describes stopped being the only way
to do them.
deedis on crates.io now, asdeed-lang, so "From source" was telling areader to clone a repository to get a binary
cargo install deed-langfetches.And the release carries
install.shandinstall.ps1. The page led with themanual unpack, which is now the long way round rather than the way.
So there is a "One line" section at the top with both one-liners, what the
checksum does and does not buy stated plainly rather than implied, and links to
both scripts: piping a script into a shell is worth being uneasy about, and the
honest answer is that they are short and in the repository. Everything the
manual path said it keeps, under "By hand instead".
deed newjoins the command table, and it opens "A first program", which untilnow told a reader to type a module header out of a web page. That transcript is
the output of the released binary, run for this change.