fix: retain completed results during live editing
This commit is contained in:
@@ -8,9 +8,9 @@ Patterns, replacement templates, test text and project files stay in the
|
||||
browser. There is no account, backend, upload, remote execution, telemetry,
|
||||
runtime CDN, remote font, or cloud-save service.
|
||||
|
||||
## Current release — 0.4.0
|
||||
## Current release — 0.4.1
|
||||
|
||||
The v0.4.0 release contains twelve selectable, executable profiles:
|
||||
The v0.4.1 release contains twelve selectable, executable profiles:
|
||||
|
||||
- **JavaScript (ECMAScript)** — the current browser's native `RegExp`, with
|
||||
ECMAScript 2025 syntax supplied by regexpp 4.12.2;
|
||||
@@ -99,6 +99,9 @@ relabeled Scala engine.
|
||||
- Parsing and execution run in separate workers.
|
||||
- Actual execution can be terminated by killing its worker.
|
||||
- The worker is recreated after timeout, crash or cancellation.
|
||||
- Live editing retains the last completed, input-bound syntax and result frame
|
||||
until the newest revision finishes. Stale frames are labelled and cannot
|
||||
enable Run, decorate current editors, or drive current-input selections.
|
||||
- ECMAScript capture ranges use the engine's `d` indices result; every other
|
||||
profile returns its native range records through a bounded fixed bridge.
|
||||
- Named, numbered, optional, empty and repeated-final captures are represented.
|
||||
|
||||
Reference in New Issue
Block a user