Reuh/anselme
1
0
Fork 0
mirror of https://github.com/Reuh/anselme.git synced 2025-10-27 16:49:31 +00:00
Code Releases Activity

Only serialize referenced upvalues in function serialization

Browse source
This commit is contained in:
Étienne Fildadut 2024-01-03 17:59:44 +01:00
parent 289f10b3c5
commit a46ac380e8
4 changed files with 41 additions and 27 deletions
Download patch file Download diff file Expand all files Collapse all files

7
ideas.md
View file

@ -22,13 +22,6 @@ Do some more fancy scope work to allow the translation to access variables defin
---
Persistence "issue": Storing a closure stores it whole environment, which includes all the stdlib. Technically it works, but that's a lot of useless information. Would need to track which variable is used (should be doable in prepare) and prune the closure (list identifiers and symbols used in children and regroup in a single exported+normal layer). The closure would also captures things like _translations that should not be persisted and prevent any update to it or its upvalues (the captured scope in the closure will not be able to be linked with the real scope in the reloaded script)...
Or register all functions as ressources in binser - that makes kinda sense, they're immutable, and their signature should be unique. Would need to track which functions are safe to skip / can be reloaded from somewhere on load. Would need to distinguish anonymous from non anonymous functions...
Or just say closures probably shouldn't be persisted. Yeah, probably easier.
---
Standard library.
* Text manipulation would make sense, but that would require a full UTF-8/Unicode support library like https://github.com/starwing/luautf8.