M7

M7 Script V2 Console

Inspect the hybrid parser without leaving the page.

Language

Execution Phase

Enter M7 Script Code

formatStatus = (status) => status || "unknown";

releaseSummary = function(
    [int succeeded, int failed, {name:service}, ...labels],
    {
        environment:environment,
        region:region,
        capacity:[int warm,,int max,...burst]
    },
    matcher = ~m/service=m7script&environment=demo/,
    normalize = (()=>(value)=>value||"unknown"),
    ...samples
) {
    return function(includeDetails) {
        return includeDetails
            ? {
                service: service,
                environment: environment,
                region: region,
                matcher: matcher,
                message: `release ${service}: ${succeeded} succeeded, ${failed} failed`,
                status: formatStatus(
                    normalize()(succeeded > failed ? "healthy" : "needs-attention")
                ),
                capacity: {warm:warm, max:max, burst:burst},
                firstSample: samples[0].latency,
                succeeded: succeeded,
                failed: failed,
                labels: labels,
                samples: samples
            }
            : formatStatus(
                normalize()(succeeded > failed ? "healthy" : "needs-attention")
            );
    };
}(
    [12, 2, {name:"m7script"}, "parser", "v2"],
    {environment:"demo", region:"us-west", capacity:[2,,8,"elastic"]},
    ~m/service=m7script&environment=demo/,
    (()=>(value)=>value||"unknown"),
    {latency:12, errorRate:0.01},
    {latency:16, errorRate:0.02}
);

summary = releaseSummary(true);

V2 accepts M7 Script only. Lex is structured; AST shows the final hybrid parse trees.

Submitting console request...

Program completed. Open the Output tab for the execution result.

There was an error handling the console request.

No output yet.

Run an M7 Script V2 Lex or AST request to inspect the parser output.

V2 Working Style

When in doubt, start with familiar JavaScript-style expressions and function syntax.
Type hints are supported. Use the bundled example as the current guide for their placement.
Destructuring goes well beyond JavaScript; use the example program as the working reference until the syntax guide is written.
Use AST to inspect V2's final hybrid parse trees without its diagnostic spew.

V2 Parser Views

tokens - structured lexer output from the pinned V2 lexer.
ast - final trees from the hybrid parser: a shift-reduce / top-down descent parser grouping system.
The console captures parser diagnostics separately, so this view stays focused on the resulting tree.

V2 Syntax Status

Type hints work. The parser accepts the current hint syntax used throughout the example program.

Return types are not ready yet. Their intended position is : rtype after a function's parameter grouping, but that path is currently bugged. Leave return annotations out of parser experiments for now.

Current Scope

V2 currently accepts M7 Script only and is a parser workbench, not an interpreter. Parser output is capped at 4 MiB.

V2 ASTs differ dramatically from V1 ASTs. The V1 interpreter is not yet compatible with V2 trees, so V2 output cannot be executed through it.

The language documentation is still being written and will grow as the parser settles. Until then, this console's example is the most reliable practical syntax reference.