Orkuncakilkaya
c804c4b0ee
stdin is read once, whole, and read_file serves a copy of it wherever the program opens <path> -
the entry, an import through a barrel, a component's .xml / .lss, an .lres. Paths match after
normalising both ('/' separators, relative under $PWD, . / .. / // folded, case on Windows);
diagnostics keep the file's usual name, with the buffer's lines and columns. A <path> nothing
opens is one warning. On ludic build it implies --check. Reseeded; bootstrap-cfree fixpoint holds.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
9 lines
667 B
Markdown
9 lines
667 B
Markdown
bump: minor
|
|
type: feat
|
|
**Check an unsaved buffer.** `ludic build --check --diagnostics=json --stdin-file <path>` (and
|
|
`ludicc --check --stdin-file <path>`) checks the program as usual, but wherever the compiler would open
|
|
`<path>` - the entry, an import reached through a barrel, a component's `.xml` / `.lss`, an `.lres` -
|
|
it reads the text on stdin instead, so an editor's diagnostics follow typing without a save. Paths are
|
|
matched after normalising both (separators, relative to the working directory, `.` / `..` folded).
|
|
Diagnostics carry the file's usual name with lines and columns in the buffer; a `<path>` the program
|
|
never opens is reported as one warning.
|