Archived
Will Anderson
48b72843e1
Add three new crates and extend the compiler and CLI toolchain: - el-manifest: el.toml manifest parser using serde + toml crate; supports package info, registry/path/version deps, build config with seal key sources, cross targets, and plugins; Manifest::find_manifest() walks up the directory tree - el-registry: HTTP registry client (reqwest + tokio) for packages.neurontechnologies.ai; PackageMetadata, fetch/download/publish/ search, BLAKE3 checksum verification, local cache at ~/.engram/packages/ - el-build: build orchestrator with incremental builds (BLAKE3 file hashes in .el/build-cache.json), cross-compilation target tagging, dep resolution, plugin registry with on_ast/on_typed_ast/on_bytecode hooks, test runner, fmt/check/clean commands - CrossTarget and NativeTarget enums with triple() and artifact_extension() methods; NativeTarget::Host detects compile-time platform via cfg! macros - Plugin system: CompilerPlugin trait + PluginRegistry; dynamic loading is a marked TODO with clear extension point for libloading - CLI extended with: new, add, remove, update, build --cross, run, test, check, fmt, clean, publish, search, plugin add/remove/list; old single-file commands moved to build-file/seal/unseal subcommands - Fix pre-existing debugger.rs borrow error (unwrap_or temporary lifetime) - Fix checker.rs and codegen.rs to handle TestDef/Seed/Assert Stmt variants - Add spec/language.md sections 12-14: package system, build system, plugin system, cross-compilation targets table 130 tests passing, zero warnings
20 lines
692 B
Rust
20 lines
692 B
Rust
//! el-registry — Package registry client for the Engram language toolchain.
|
|
//!
|
|
//! The registry is at `https://packages.neurontechnologies.ai`. This crate
|
|
//! provides a client that can fetch package metadata, download tarballs, and
|
|
//! publish packages.
|
|
//!
|
|
//! Local package cache: `~/.engram/packages/{name}/{version}/`
|
|
//!
|
|
//! # Note
|
|
//! The registry server does not yet exist. The client is implemented to the
|
|
//! planned API contract and will work once the server is deployed.
|
|
|
|
pub mod client;
|
|
mod error;
|
|
mod resolve;
|
|
|
|
pub use client::{cache_dir, PackageMetadata, RegistryClient, DEFAULT_REGISTRY_URL};
|
|
pub use error::{RegistryError, RegistryResult};
|
|
pub use resolve::resolve_deps;
|