fix tickSafeMode bug, change some apis to allow users to customize #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recently, I've been working on a project that utilizes your time-wheel timer, and I must say it works exceptionally well and efficiently. In particular, I'm very impressed with the TickSafeMode feature - it's a brilliant idea. However, during the course of using it, I've come across a few minor bugs related to TickSafeMode, and sometimes I need the remove function to return a meaningful value when dealing with potentially timeout-prone asynchronous transactions. Additionally, I believe it would be beneficial to allow users to customize the buffer size for TickSafeMode.
I have made some modifications to address these issues and updated the tests accordingly. I would greatly appreciate it if you could take a look at my changes and provide any feedback or suggestions.