Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
BehaviorInterceptor and state #26706
Currently a user could be tempted to add mutable state to an interceptor, but the instance will be shared for each spawned actor where it is used.
I think we should either clearly document that you must not put mutable state in it, or make
It is possible we have existing internal interceptors where this has been missed (timers, supervision)