AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
翻譯準備中
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
Like Elm, but different species.
Zelkova is my attempt to understand how one could build a functional programming language compiling to web assembly. It is strongly inspired by Elm, with some Haskell addition here and there.
Do not expect any production-level code here, I'm just trying to understand how a compiler works :)
Here is a list of resources I consulted while working on this project.檢視完整 README ↗Like Elm, but different species.
Zelkova is my attempt to understand how one could build a functional programming language compiling to web assembly. It is strongly inspired by Elm, with some Haskell addition here and there.
Do not expect any production-level code here, I'm just trying to understand how a compiler works :)
Here is a list of resources I consulted while working on this project.
https://github.com/RustPython/RustPython/blob/master/parser/src/python.lalrpop
https://github.com/gluon-lang/gluon/blob/master/base/src/ast.rs
https://github.com/gluon-lang/gluon/blob/master/parser/src/grammar.lalrpop
http://smallcultfollowing.com/babysteps/blog/2016/03/02/nice-errors-in-lalrpop/
https://github.com/elm/compiler/blob/master/compiler/src/Parse/
https://github.com/elm/compiler/blob/master/compiler/src/AST/Source.hs
https://github.com/tcr/rust-hindley-milner/blob/master/src/lib.rs
https://github.com/0b01/tensorscript/tree/master/trsc/src/typing
https://rickyhan.com/jekyll/update/2018/05/26/hindley-milner-tutorial-rust.html#
Wand algorithm is a simpler version of Hindley-Milner (different trade off though)
1 The Elm compiler (0.19) is based/inspired by those papers and books.
The above references ended up unused because of the amazing petgraph library.
The language itself is specified under docs/spec/, one chapter
per file, starting from that directory's index. It is normative — it describes
Zelkova as designed, not just what the compiler happens to accept today — and every
code example in it is checked against the compiler by cargo test --test spec, so a
chapter that drifts from the compiler is a red test rather than a stale sentence. It
is published, alongside a landing page and the rendered rustdoc, at
francois.monniot.eu/zelkova-lang/.
cargo doc documents the compiler's own Rust, not the language — that's the rustdoc
published above. docs/tickets/ is the compiler's work log, not documentation for
someone writing Zelkova, and stays unpublished; read it on GitHub.