almide check fails on this repository's default branch (cb99efc16) with almide v0.65.0, the latest release. The same failure happens on almide develop and on v0.64.0, so this is code that has fallen behind the language. It is not a new compiler regression. The almide downstream canary (almide/almide#2852, part of almide/almide#2839) found it. The canary builds public downstream projects with each release candidate. Commands that fail: check, test.
First diagnostic (almide check, v0.65.0; 2 error line(s) in the log):
error[E002]: undefined function 'json.keys'
--> src/mod.almd:51:18
in call to json.keys()
here: let header = json.keys(first)
hint: No function 'keys' in module 'json'. See docs/CHEATSHEET.md for available functions
|
51 | let header = json.keys(first)
| ^^^^^^^^^
error[E002]: undefined function 'value.get'
--> src/mod.almd:54:61
in call to value.get()
here: header |> list.map((h) => escape_cell(value.as_string(value.get(row, h) ?? value.null()) ?? "")) |> list.join(",")
Reproduce:
git clone https://github.com/almide/csv && cd csv
almide --version # almide 0.65.0
almide check
The diagnostic's own hint names the migration. almide fix applies the machine-applicable ones (for example .. to ..<). While this is open, the canary reports the project as a pre-existing failure. Once it builds again, the project is recorded as known-good, and a later break counts as a regression.
almide checkfails on this repository's default branch (cb99efc16) with almide v0.65.0, the latest release. The same failure happens on almide develop and on v0.64.0, so this is code that has fallen behind the language. It is not a new compiler regression. The almide downstream canary (almide/almide#2852, part of almide/almide#2839) found it. The canary builds public downstream projects with each release candidate. Commands that fail: check, test.First diagnostic (
almide check, v0.65.0; 2 error line(s) in the log):Reproduce:
The diagnostic's own hint names the migration.
almide fixapplies the machine-applicable ones (for example..to..<). While this is open, the canary reports the project as a pre-existing failure. Once it builds again, the project is recorded as known-good, and a later break counts as a regression.