neuron-explorer
Steering-first neuron explorer for Qwen3.5-4B: push every MLP neuron, keep every rollout, browse the results
Write functional code that compiles to WebAssembly
Translation pending
AI summary · website and README
Developer toolsRust · JavaScriptGitHub @fmonniotOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
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.Read the full 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.