Skip to content

Move Tell toward typed Go runtime and native GPUI Studio - #15

Merged
Neonwave175 merged 4 commits into
mainfrom
feat/native-typed-runtime-gpui-studio
Nov 18, 2026
Merged

Neonwave175 merged 4 commits into
mainfrom
feat/native-typed-runtime-gpui-studio

Conversation

@KernelGhost-gif

@KernelGhost-gif KernelGhost-gif commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

Summary

This begins the migration proposed by Bhuvan: make the native Go implementation the primary runtime, introduce typed Tell syntax, deprecate the Python runtime/IDE, and start the Rust GPUI editor.

1. LLVM workflow cost

  • Remove pull-request triggers from the TellC LLVM/LLD workflow.
  • Keep the full Linux, Apple silicon, and Intel macOS toolchain matrix on weekly schedule and manual dispatch.
  • Keep fast Go/native checks on normal PRs.

2. Typed Go dialect

  • Add type-first variable declarations such as let number result be 42.
  • Add explicit function signatures such as to factorial(number: n) out number:.
  • Add strict --typed validation for run, check, and build.
  • Validate typed function parameters and return values at runtime.
  • Preserve typed signatures in the bytecode artifact so compiled execution retains the checks.
  • Preserve the existing dynamic syntax as the default for backwards compatibility.
  • Add a native-only example and regression tests.

3. Python/Tk deprecation

  • Mark the Python interpreter and Tk IDE as deprecated compatibility components.
  • Remove the separate tell-ide entry point from new Python package installations.
  • Keep python -m tell ide temporarily available with a deprecation warning.
  • Document the migration and compatibility-only policy.

4. Rust/GPUI Studio

  • Add a native Rust desktop application under studio/.
  • Initial single-file editor supports UTF-8-safe cursor movement, text insertion/deletion, save, and running through the Go CLI.
  • Pin the GPUI dependency to a specific upstream Zed commit.
  • Add a weekly/manual GPUI build workflow rather than putting its substantial dependency build on every PR.
  • Document missing editor features and explicitly avoid claiming lower memory/CPU use until benchmarked.

Compatibility and performance status

This is a staged migration. Python is not deleted, and the typed dialect is opt-in. The Go runtime still uses the existing dynamic value representation; this PR adds typed validation and carries function contracts into bytecode, but does not yet claim faster execution or compilation. Type-directed bytecode specialization and performance benchmarking are a follow-up phase.

The new GPUI app is an initial editor foundation rather than a complete Zed replacement. Memory and CPU improvements need measurement.

Validation

The native Go tests/race detector/vet, Python compatibility tests, and combined test/build workflow have passed. Linux and Windows validation have passed. The macOS runtime-package job is still queued at the last check. Full LLVM and GPUI toolchain builds are available through their scheduled/manual workflows.

@Neonwave175

Copy link
Copy Markdown
Collaborator

Thanks

@Neonwave175
Neonwave175 merged commit 155be4d into main Nov 18, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants