The Prove view gives each routine 3 seconds on the clock. On a slow or busy device that runs out before the proof does, and claims stay open with nothing to say why. - The view says when the time, not the proof, stopped the checker, that what was not finished is open and not disproved, and offers to prove again with the next longer time. The setting is at the foot of the view: 3, 10 or 30 seconds or 2 minutes for each routine, kept in the browser (pplus.proveclock). - A proof rendered with Quarto takes prove-seconds on the shortcode or pplus-prove-seconds for the site, and the render warns when the time ran out. - The home page's own example is proved with no time on the clock, and the tests that hold a proof's outcome give it time to spare, so neither depends on the machine. - core moves to 38e6e2c, whose report says which routines the clock stopped.
This commit is contained in:
19 files changed
+240
-6
No files matched your search
@@ -47,6 +47,7 @@ syntax-definitions:
|
||||
pplus-engine: ../programming-plus # a built Programming+ (its folder, or its dist/)
|
||||
pplus-url: "https://pplus.scient.ing" # where the live views point (this is the default)
|
||||
pplus-strict: true # optional: a view that cannot be rendered, or a run that does not print its EXPECT lines, stops the render
|
||||
pplus-prove-seconds: 30 # optional: the seconds the prover has for each routine of a rendered proof (default 3)
|
||||
```
|
||||
|
||||
`mojo.xml` is generated from the same words as the Mojo pane's highlighter (the compiler's own token table, at the pinned Mojo version). A printed listing therefore colors `mut`, `deinit`, the transfer `^`, and removed words such as `fn` exactly as the pane does. If the project already has its own `pseudo.xml`, keep that and add only `lingo.xml`.
|
||||
@@ -122,10 +123,13 @@ And these work with the rendered ones:
|
||||
| `height` | the live frame's height when it is put in place (default 520; 720 for translate and the machine's views, which open the whole playground) |
|
||||
| `follow` | steps: the variables to show, comma-separated |
|
||||
| `max` | steps: the most steps kept (default 400; from 10 to 5000) |
|
||||
| `prove-seconds` | proof: the seconds the prover has for each routine (default 3, or the site's `pplus-prove-seconds`) |
|
||||
| `to`, `layout` | translate: the notations to show, comma-separated; `tabs` (default), `columns` or `grid` |
|
||||
| `compiler` | run, for a Mojo file: `auto`, `on` or `off` |
|
||||
| `column` | Quarto's column for the view (`page`, `screen`, `margin`, ...) |
|
||||
|
||||
**A proof has a time limit.** The prover's work is counted and is the same on every machine, but it also stops at a time on the clock, 3 seconds for each routine as in the app, and a page is rendered once on whatever machine builds the site. If that machine is slow or busy, 3 seconds can run out before the proof does: the page then shows claims open that are provable, with a "Time ran out" note, and the render warns (`proof: time ran out on ...`). Give the prover more with `prove-seconds="30"` on the shortcode or `pplus-prove-seconds: 30` for the site; more time never proves anything that is not true. A result is kept in `.quarto/pplus/` by its request, so a new time renders again.
|
||||
|
||||
In a format other than HTML (a PDF, a Word file), a rendered view becomes Markdown. The run is printed as a code block; the steps, the table of values and the machine's counters as tables; the proof, tests and checker's findings as lists; and translate as one listing per notation. The flowchart, the data flow and the lifetimes say they are drawn in the HTML version. A view of the machine gives the registers the run has written by step `t` and names the cards drawn in the HTML version. Each view except translate is followed by a link to the app.
|
||||
|
||||
### The live views, arranged
|
||||
|
||||
Reference in new issue
Block a user