Orkuncakilkaya
4499cedcb8
The encoder appends into RtJsonState's buffer (grown only past the biggest document yet): ints and Q16.16 fixeds written as digits in place, floats through string() and freed. Json.encode copies the answer out once; Json.write_file hands the buffer to Fs.write_text (.tmp + rename) and keeps nothing. json_saves.ludic: exact text, the file equals encode, parse round-trips, 1000 saves grow 0; clean under MallocScribble. json_quote (the + builder) is gone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 KiB
1 KiB
| id | name | category | kind | tokens | sig | tip | order | ns | member |
|---|---|---|---|---|---|---|---|---|---|
| json-write_file | Json.write_file | json | namespace-method | Json.write_file | Json.write_file(value, path) -> bool | Write a value tree to a file as JSON, keeping nothing. | 5 | Json | write_file |
Writes the tree as the same text Json.encode would give, straight to path: to path.tmp first and then renamed over it, as Fs.write_text does, so a crash mid-write leaves the previous file whole. The text is built in a buffer the runtime keeps and grows only for a document bigger than any before, so a game can save as often as it likes and hold nothing more for it - where Json.encode hands back a string of its own every time. False when the file cannot be written.
program Save {
entry {
let o = Value.object()
Value.put(o, "day", Value.int(3))
let path = Os.temp_dir() + "/save_doc.json"
print(Json.write_file(o, path))
Fs.remove(path)
}
}