The first -- ends the name of a custom command, and a line of s(...) reaches the shell unchanged. Written for the Tazel release that carries tazel#40.
They were produced again with a real build, and they match, the LLVM IR included.
The command line page adds --sysroot, --incremental, --static-talart-library, --test and the size levels, with sections on incremental and test builds, in all four languages. The record of a check now names Tala 0.2.0. The comment on the terminal samples says what was checked: their messages against the source of Tala 0.2.0, while the LLVM IR comes from an earlier build.
They said version 0.1.0 is built with the compiler of Tala 0.1.0, which stopped being true with the next release of each. What holds for every version is that a tool accepts what its compiler accepts.
Test suites work, so the note no longer lists them. The commands page adds fetch, custom, the build cache, remote serve and the daemon, with sections on spending the machine and on custom commands. The project file page adds the execution block, the size levels and the shape of a version. All four languages.
The build that serves tala.run, talac.tala.run and tazel.tala.run now also serves the formatter and the linter, chosen by host name like the others. Each site has a landing page and two documentation pages in en-US, de-DE, ru-RU and he-IL: - talafmt: the command line (inputs, --check, --emit, exit status 2 for an unreadable line) and what it changes (indentation, line endings, trailing whitespace, the final newline; protected text; encodings from talafmt.kts). - talalint: the command line (--fix) and what it checks: the compiler's diagnostics as compiler.<code>, and format.trailingWhitespace, format.mixedLineEndings and format.missingFinalNewline. --fix rewrites a file with talafmt's default layout, which also re-indents blocks. The facts follow the READMEs of Progmasoft/talafmt and Progmasoft/talalint 0.1.0 and the talalint source. site.ts lists the sites once, with their names, so the header, the landing page and the documentation shell no longer keep their own copies. Each host has its robots.txt and sitemap.xml, nginx gains the two server blocks, and the tests check the new hosts like the others.
Tazel moved out of Progmasoft/tala into Progmasoft/tazel (tala#93), so the "Source" link at the end of the Tazel landing page pointed at a directory that no longer exists. In all four languages it now opens https://github.com/Progmasoft/tazel. The Tala and Talac pages keep their links into Progmasoft/tala.
tala.run, talac.tala.run and tazel.tala.run now each open on a landing page of their own. talac.tala.run and tazel.tala.run used to redirect "/" to their first documentation topic. Every landing page has one headline, two ways in, a "Why Tala?", "Why Talac?" or "Why Tazel?" section of tabs over one code panel, and a short row of next links. The tabs follow the ARIA tabs pattern: arrow keys, Home and End move between them. The code panel stays left to right on the Hebrew pages and has a copy button. Every sample is something that works today. The Tala tabs show HelloWorld and PrimeNumbers, which are copies of Examples/ (a test compares them), a small program that shows an argument evaluated by need, the LLVM IR that talac -O2 made of the gcd loop of Examples/GCD, and a Tazel project file. The Talac tabs show the terminal output of talac 0.6.0 for one command, --emit=metadata, each --emit stage, the optimized IR and a type error. The Tazel tabs show the project file, the everyday commands, target selection, lock graph and a did-you-mean hint. Of the fifteen programs in Examples/, talac 0.6.0 builds four (HelloWorld, GCD, PrimeNumbers, CollatzTrace), so the classes, generators and pattern matching of the others are not shown yet. The old home page said in nearly every paragraph that the work was unfinished, linked "Why Tala?" three times, and numbered its sections. It is gone. The state of the project is said once, as a small badge beside the name in the header. The header no longer repeats a Home link, since the name leads home. On talac and tazel it lists their documentation topics. Styles that only the old home page used are removed. The titles and descriptions of "/" come from the landing content of each site, and the talac and tazel sitemaps list "/". The tests follow: siteHome is "/" everywhere, the tazel canonical path is "/", and the example comparison reads the landing samples.