-
Notifications
You must be signed in to change notification settings - Fork 309
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
Refactor Observer and LimitEnforcer cleaner for... #3114
base: main
Are you sure you want to change the base?
Conversation
8a34223
to
b026443
Compare
9349b16
to
f5bc217
Compare
More info on internal PR #9192 |
Much of this is basically a revert of #3034 for an even cleaner implementation. |
This will return ownership over limitEnforcer from the api class to the isolate class.
This will allow for better separation of responsibilities between the two.
f5bc217
to
d7ad08e
Compare
@@ -305,11 +307,11 @@ class Worker::Isolate: public kj::AtomicRefcounted { | |||
kj::Maybe<ValidationErrorReporter&> errorReporter = kj::none) const; | |||
|
|||
inline IsolateLimitEnforcer& getLimitEnforcer() { | |||
return limitEnforcer; | |||
return *limitEnforcer; | |||
} | |||
|
|||
inline const IsolateLimitEnforcer& getLimitEnforcer() const { |
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.
Non-blocking nit: We have the kj::Rc<T>
and kj::Arc<T>
types now for safer handling of references to refcounted and atomic refcounted types. It would be nice if we could start working on replacing uses of bare references for these where it's not too cumbersome of a change.
isolate pools