-
Notifications
You must be signed in to change notification settings - Fork 492
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
WalletFilterProcessor
: Minor refactoring
#12170
WalletFilterProcessor
: Minor refactoring
#12170
Conversation
_lastProcessedFilter = value; | ||
} | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain why is this important please? I do not understand it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because LastProcessedFilter
is accessed from multiple threads. In that situation, lock (..)
or any other synchronization primitive should be used.
It serves also as a self-documentation that something like that actually happens.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR improves a few minor things that I noticed while researching #12148.
Please review commit by commit (each one can be a mini PR).