Development documentation · Some APIs may be unreleased Published release →

About neoCLR

neoCLR is an open-source project developing a managed runtime, a class library and tools for Raven applications. It was initiated by Marina Sundström and is available under the MIT license.

Who Raven and neoCLR are for explains the modern .NET-inspired programming experience, intended audience and library compatibility boundary.

Project scope

The platform brings compilation, execution, application APIs and editor support together. Raven programs use modules to organize code and access libraries for text, collections, files, Tasks, networking and HTTP. The runtime manages memory and supplies the services those libraries need.

The goal is fast native web and backend development with familiar C#/.NET ergonomics, competitive with Go and modern JavaScript runtimes in simplicity, productivity and speed. Concurrency is central to that direction. Raven is the current frontend; other languages and workloads are future goals. These are ambitions, not measured performance rankings or additional shipped capabilities.

The project is experimental. The installation guide describes the available toolchain; feature guides explain supported behavior and practical limits.

Relationship to .NET

neoCLR uses familiar managed-platform concepts: values and objects, generics, interfaces, metadata and garbage collection. Its runtime and class library are independent implementations. UTF-8 text and explicit Optional/Result outcomes are important parts of its programming model.

Raven can target both .NET and neoCLR, each with its own library contracts. neoCLR does not run arbitrary .NET applications. See the platform comparison for the differences that affect programs.

How it works

The runtime is implemented in Rust. Raven supplies the source language, compiler and editor integration. The interpreter executes neoCLR assemblies; a developing ARM64 AOT backend compiles supported applications into standalone executables.

Architecture introduces these layers, and metadata explains how compiled libraries connect tools and execution.

Project direction

The project develops through working applications and library use cases. Project direction summarizes open areas such as broader native execution, HTTP capabilities and module features. These are areas of work and exploration, not a release schedule.

Contributing

Run a sample, report a problem, improve a guide or propose a change with a concrete use case. For substantial contributions, open an issue to discuss scope.

Source and pull requests · Issues and questions

The website explains the platform and how to use it. The repository's documentation contains implementation contracts, design research, validation procedures and development history for contributors.