- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
"throw new KillActorControl"
[...pondering other standard library optimizations...]
This is littered through the actor code. Since this is really a control-flow statement, is there a reason it's not throwing a singleton (whether an object or val doesn't really matter) rather than repeatedly creating new instances?
By contrast, Breaks contains a val with a singleton for breakable/break.
This is littered through the actor code. Since this is really a control-flow statement, is there a reason it's not throwing a singleton (whether an object or val doesn't really matter) rather than repeatedly creating new instances?
By contrast, Breaks contains a val with a singleton for breakable/break.
Re: "throw new KillActorControl"
Ignore the above. I misread the code and was conflating KillActorControl with Actor.suspendException.