neuron-explorer
Steering-first neuron explorer for Qwen3.5-4B: push every MLP neuron, keep every rollout, browse the results
翻譯準備中
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Bock is a feature-declarative, target-agnostic programming language
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
A feature-declarative programming language. Compiles to JavaScript, TypeScript, Python, Rust, and Go. No runtime to ship.檢視完整 README ↗
A feature-declarative programming language. Compiles to JavaScript, TypeScript, Python, Rust, and Go. No runtime to ship.
A function in Bock declares what it does, what types it operates on, what
effects it has, and what guarantees it requires. Annotations and
signatures carry the intent; the body carries the work. The compiler
resolves the rest. A function annotated @concurrent becomes
Promise.all in JavaScript, tokio::join! in Rust, and goroutines in Go.
An effect declared with with Log becomes a structured logger parameter
in every target. The same source describes the program. The compiler
describes how each target should run it.
Most cross-platform languages add a runtime: a virtual machine, a
translation layer, a library your program depends on at execution time.
Bock does not. The output of a bock build is plain code in the target
language, ready to drop into your existing project. Run it on Node, ship
it as a Python package, link it into a Rust binary, deploy it as a Go
service. The Bock runtime supports development; it does not ship.
Bock is at v1.0 and under active development. The compiler pipeline runs
end to end: the CLI (bock) scaffolds, checks, builds, runs, tests, and
formats projects; the interpreter executes source directly for fast
iteration; codegen emits all five targets as per-module native source
trees; the v1 standard library (11 core modules) executes across every
target; and the website and VS Code extension build from this repo. The
work in flight is codegen polish for real-world programs: a focused
conformance suite passes on all five targets, while the broader example
programs are being hardened target by target (tracked in
STATUS.md and ROADMAP.md).
AI participates in compilation, not at your program's runtime. The
pipeline is deterministic from parsing through type checking, ownership
analysis, effect tracking, and target lowering; an [ai] block in
bock.project is the opt-in seam where the compiler may consult an AI
model at capability gaps, with deterministic fallback and pinned replay
in production builds. This path is configured but not yet exercised in
real-world usage; Bock uses rule-based code generation by default.
Additional codegen targets (Java, C++, C#, Swift) are roadmap candidates
for after v1, not v1 commitments.
A function declares its effects in the signature. Here prepare says it
uses Logger; the handler is injected at the call site rather than
imported as a global. The body is a pipeline.
module main
public record Document {
text: String
quality: Float
}
public effect Logger {
fn log(message: String) -> Void
}
public fn normalize(doc: Document) -> Document {
Document { text: doc.text.trim().to_lower(), quality: doc.quality }
}
public fn keep_quality(docs: List[Document]) -> List[Document] {
docs.filter((d) => d.quality > 0.5)
}
public fn prepare(docs: List[Document]) -> List[Document] with Logger {
log("preparing ${docs.length()} documents")
docs
|> keep_quality
|> ((ds) => ds.map(normalize))
}
Bock ships as a single binary. Install with Cargo, or download a pre-built binary from GitHub Releases.
cargo install bock
bock --version
Scaffold a project, then check, build, and run it:
bock new hello
cd hello
bock check # type-check, lint, validate context
bock run # execute via the interpreter (no codegen)
bock build --target js # emit JavaScript into build/js/
bock build --target go # emit Go into build/go/
bock new generates bock.project (TOML), a src/main.bock entry
point, a tests/ directory, and a .gitignore. The bock.project
includes a commented-out [ai] block; AI-assisted generation is opt-in.
The compiled output runs on its target with nothing from Bock imported at
runtime: node build/js/main.js prints the program's output directly.
The full walkthrough is at bocklang.org/get-started.
| Path | Contents |
|---|---|
compiler/ | The compiler, a Cargo workspace of bock-* crates plus the bock CLI, and the conformance suite. |
spec/ | The language specification (spec/bock-spec.md) and its dated changelogs. |
stdlib/ | The Bock standard library (core.* modules), shipped as source. |
extensions/vscode/ | The VS Code extension, with vocabulary synced from the compiler. |
examples/ | Example Bock projects, from fundamentals to real-world shapes. |
docs/ | The mdBook documentation source. |
website/ | The bocklang.org marketing site (Astro). |
branding/ | Brand assets. Most content is gitignored; branding/assets/logo/ is committed for contributor access. |
docs/spec/bock-spec.mdARCHITECTURE.mdROADMAP.md, STATUS.mdBock is at v1.0 and contributions of every size are welcome. Start with
CONTRIBUTING.md for local setup and the workflow, and
ARCHITECTURE.md for a tour of the compiler pipeline.
Participation is governed by the Code of Conduct.
Bock is open source under the MIT License.