-
Notifications
You must be signed in to change notification settings - Fork 1
linter produces some warnings #3
Comments
Overhelming :-( If you would like to volunteer and send me bite sized PRs to incrementally fix the non-cosmetic items, I would be more than happy to review, test and merge them when ok. |
Some questions:
|
Wow! Thank you very much. This will need some time, hopefully this weekend...
I would say no, but the client code must manually deallocate anything unused/unreachable otherwise the storage will leak space. However, if there is free space in the middle of a So the more precise answer is that any free space at the end of the DB is automatically freed, while any free space in the middle of a DB is hopefully eventually allocated again when the ratio of inserts to deletes gets positive again. Admittedly, that may never happen after some initial burst. To rearrange allocated objects such that no free space is left in the middle of the DB is not directly feasible by
and there's enough free disk space to switch to the new (out-of-place) DB. |
Only now seeing the edited post with the added question, will look into it too. Unfortunately, GitHub does not send any notifications when a post is edited and I replied to the original one only. I suggest to simply add a new message in this cases. |
All PRs merged, BTree issue tracked separately in #12. Closing, but please feel free to let me know if there's some oversight. Thank you. |
Running
gometalinter --deadline=10s "./..."
produces the following output. Some are cosmetics, but unchecked errors, shadowed vars might be hiding bugs.The text was updated successfully, but these errors were encountered: