API reference
Browse the neoCLR class library: modules, types, functions and constants, with Raven signatures and member contracts. Modules form namespaces and are the primary way the library is organized.
Browse all modules · Module guide · Feature guides
Use the API browser to find a module or type, or search for a name. Module pages list their types, functions and constants; type pages list their members. Open a member for parameters, return values, errors and usage notes.
Media type structure, typed presets and Content-Type parsing are available in the HTTP module (development).
Find an API
Development interpreter APIs: System.Slice, ReadOnlySlice, Memory and ReadOnlyMemory.
Using the reference
This reference follows the development class library. Individual pages describe concrete limits and identify APIs that differ from the published preview. Use the matching toolchain when trying development APIs.
Signatures use Raven notation. The structural type families guide explains Array, Function, Tuple, Union and Intersection. The reference support notes cover signatures that need a manual entry or additional explanation.
For an introduction and working examples, start with the feature guides. The reference provides the detailed contracts you need while writing code.
Runtime and tooling APIs
These references are for runtime control, host integration and compiler tooling:
- Garbage collection: object counters, explicit collection and KeepAlive.
- Runtime failures: terminal faults and host diagnostics.
- Raven testing project: development test APIs, data, categories and runner contracts.
- Raven benchmarking project: independent benchmark APIs, argument rows and worker contracts.
- Runtime hosting: experimental Object-root load contexts.
- .NET metadata tooling: the host library for reading and writing native metadata; this is not an application API.
- Compiler services and async builders.
Development API migration annotations use ObsoleteAttribute, with nullable migration messages and compiler warning/error severity.
Sequence indexing and slicing documents the development Index/Range extension and list contracts, copy semantics and safe alternatives.
Development: TLS stream APIs and HTTP integration.
- Key/value pair equality and hashing: development generic record contracts and current limits.
The separate development Neo.Signals extension documents its subscription-only view and signature-dependent publishing method. See also typed function invocation.