3 ms·
> very useful nasty parts: on-stack replacement (OSR) ... > Generally, this doesn't matter much, but there are some cases where it's really inconvenient. If y
by mraleph 14y ago
> very useful nasty parts: on-stack replacement (OSR)
...
> Generally, this doesn't matter much, but there are some cases where it's really inconvenient.
If you have a real world application [not a microbenchmark] that suffers from the fact that Dart VM does not implement OSR please add it to https://code.google.com/p/dart/issues/detail?id=6787 https://code.google.com/p/dart/issues/detail?id=6787
- ahoge 14y agoOne could argue that every application which would benefit from OSR is essentially a micro benchmark. I can't disagree with that, because that statement is absolutely true. The only difference between those two kinds of programs is the intention of the programmer. In both cases you have at least one heavy function which is called just once. As far as the VM is concerned, there is no difference whatsoever. But it's also true that there are sometimes long running functions which are aren't frequently called. In Java, JavaScript, or C# you won't have to worry about that kind of thing. You won't have to break it down in smaller pieces just for the sake of spreading the load across more function calls.
- mraleph 14y agoMy point is: you don't have to worry in Dart either. If the code you are shipping is suffering due to the lack of OSR and you have to work around that --- just add an example to the bug and we will fix it.