| |
|
|
|
|
|
| |
the next parse starts from it, so a new line's indent in a 9k-line Zig file costs the 0.2 ms of what the edit touched, not the 47 ms of a parse anew (3.5 ms → 0.5 ms for 400 lines); not while a rollback copy holds the tree, which an edit in place would change under the copy: that one is left as it was and parsed anew, as is one whose revision moved without it (a twin's edit), by node_tree_edits, the revision its edits reach
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge
|
|
|
grammar has an indent query, its indent_for_newline over the file's tree (indent.zig: the reference's containment engine, every capture and predicate the vendored queries use, the hybrid heuristic), else acme's copy as before; and Enter between a pair puts the closer on a line of its own at that indent and the cursor on one a level in, as helix's insert_newline does, in plain text too
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge
|