neuron-explorer
Qwen3.5‑4B 전용 조향형 뉴런 탐색기, 모든 MLP 뉴런을 밀어 결과를 보관·탐색
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기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.