Point at the page that answers instead of describing - #955
Merged
Conversation
Stage 1's second item is done: <https://deed-lang.github.io/agents/>. It had been one paragraph on the install page, which is not where somebody deciding whether to wire a compiler into an agent is reading. The page fills every transcript in from the pinned compiler in the reader's tab, so it cannot claim an answer this compiler does not give: an obligation line carrying a tier, a `guarded` one with its reason, the `export` repair with its note, and a property generated from a contract in a module with no tests. The how-to now points at it, because seeing the answers is cheaper than configuring a server to find out what they look like.
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
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.
Stage 1's second item: https://deed-lang.github.io/agents/ (site
deed-lang/deed-lang.github.io#42).
deed mcphad one paragraph, on the install page. That is not where somebodydeciding whether to wire a compiler into an agent is reading.
The page does not describe what comes back, it shows it. Every transcript on it
is filled in by the pinned compiler running in the reader's tab, for the program
printed above it, so it cannot claim an answer this compiler does not give:
provenandtestedin the same answer;guardedwith"reason": "nothing narrowed this name";exportdiagnostic with its machine-applicable edit and the note sayingwhy the word does not exist;
deed_testrunning a property generated from a contract, in a module with notests in it.
The benchmark from #954 is there as a table with the control arm beside it and a
link to
benchmarks/RESULTS.md, with the three things it does not establishstated rather than dropped.
This PR is the two lines in this repository that follow from that: the roadmap
item, and a pointer from
how-to/let-an-agent-use-the-compiler.md, becauseseeing the answers is cheaper than configuring a server to find out what they
look like.