-
-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: port the performance improvements of fastbin back to pycasbin #285
Conversation
@Nekotoxin please review |
2f41a72
to
01e3200
Compare
Signed-off-by: terry-xuan-gao <[email protected]>
01e3200
to
7216844
Compare
1ec7cca
to
a7ed0bb
Compare
Signed-off-by: terry-xuan-gao <[email protected]>
a7ed0bb
to
ca8bef0
Compare
@wakemaster39 @gerbyzation plz review |
Signed-off-by: terry-xuan-gao <[email protected]>
I'm not going to review this as I pivoted away from pycasbin years ago after I reported the issue and have not been looking at casbin code since. The only remark I'd like to leave is around documentation, this PR simply refers to fastbin but I think the constrains and performance considerations are worth documenting properly. |
It has been implemented in #318, so close it now. |
Hi friend, I have just reviewed the #318 , it is very good.
I think this means respect, the respect of one coder for another coder's nice idea and hard work. It is not cool. |
Signed-off-by: terry-xuan-gao [email protected]
Description
Related Issues
Fix: #71
New Behavior
The first thing I need to say is that the idea of all the work I do in this PR comes from fastbin, thanks to his work💡
_cache_key_order
has been added to theCoreEnforcer
class, which defaults to beNone
Test