On 11-05-25 09:09 PM, Nicholas "Indy" Ray wrote:
I am a bit frustrated that in the absence of data we are selecting the more
expensive option which is also the more expensive to backtrack and following
the examples of the least successful languages.
Maybe I don't understand the subject very well, but shouldn't backtracking
from the choice of implementing M:N simply involve limiting it to 1:1, and
turning off the code that emits yield statements? Thus making actual
benchmarking possible. While that will cost the work to implement it still;
Clearly that should be worth getting the actual performance data, right?
Not turning off the yields. Just setting them to "only yield when
actually canceled" rather than "yield when time slice expires". Simpler
case, even: pure runtime policy choice.
-Graydon
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
