A potential solution to avoid re-entering past entries with FileAccess.seek_end

[Eli-bec]

I am searching for a logging system for Godot for my project, and I am considering using GoLogger because it is sufficiently documented. I found the following description under the "Managing .log file size" section of "README.md".

A potential pitfall to consider when logging large/growing data is how Godot's FileAccess API handles file writing. The FileAccess.WRITE mode truncates(deletes) the file's content, meaning we can't simply add new entries to a file. The plugin first reads the file and stores each entry in an array which are then re-entered sequentially before appending a new entry. This process can cause performance issues as the entry count grows, potentially leading to stuttering and/or slowdowns.

I think it may be possible to avoid re-entering the entries with the seek_end method provided by the FileAccess API, though I haven't tested it.

[Burloe]

Unfortunately, the reason entries are re-entered isn't due to the cursor position or anything like that. Anytime you open a file using FileAccess.WRITE, the contents of the file is deleted entirely.

However, before the latest release I looked into using FileAccess.READ_WRITE which doesn't truncate the file. Though this mode had its own caveats which added a lot of code to manage the cursor position, like you suggested. It required me to rewrite most the framework, so I opted to continue using WRITE. I might change that in a future update though.

I do appreciate the suggestion though and don't hesitate to leave others if you think of any improvements!