lint lines in package.ludic - one_statement, max_file_lines, max_function_lines, max_comment_lines, max_header_lines, paths, baseline - checked by ludic-fmt --check <files> and ludic-fmt --lint (the project), at the line; a baseline ratchet lets a rule arrive in a codebase that breaks it (--init-baseline), lowered as it is fixed. check-impl reads the alias declarations too (it had been blind to every namespace L6 moved out of the compiler), and eight methods get their pages; a test holds the formatter to keeping type arguments together (L5). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
684 B
684 B
| id | name | category | kind | tokens | sig | tip | order | ns | member |
|---|---|---|---|---|---|---|---|---|---|
| fs-write_bytes | Fs.write_bytes | fs | namespace-method | Fs.write_bytes | Fs.write_bytes(path, data, count) -> bool | Writes the first count bytes of a []byte to a file. | 12 | Fs | write_bytes |
Writes the first count bytes of data to path, replacing the file, and answers whether all of them were written. count is clamped to the slice's length.
Parameters:
path— the file to writedata— a[]byte, e.g. frombuffer(n)count— how many bytes of it
program Save {
entry {
let b = buffer(2)
b[0] = 72
b[1] = 105
print(Fs.write_bytes("hi.bin", b, 2))
}
}