News for hackers. Stuff that matters.
Re:How fast can we make interpreted Python? (2013) by sorenjan on Monday April 18, 2016 @03:46PM (#11522635)
I've never used Rust, how would it compare to a C++ solution?
Re:How fast can we make interpreted Python? (2013) by grayrest on Monday April 18, 2016 @04:21PM (#11522886)
The standard response from the Rust team is that Rust should match or beat non-SIMD C++ performance and if it doesn't, you should file a bug.

Note: The first thing anybody will ask when you complain about Rust being slow is whether you compiled with optimizations turned on (`cargo build --release`) since it tends to make a 10-15x difference.

Re:How fast can we make interpreted Python? (2013) by im_down_w_otp on Monday April 18, 2016 @04:58PM (#11523104)
Theoretically the Rust borrow-checker also knows enough about your code's protection and dispatch semantics such that additional information could be used to create deeper optimizations than are available in either C or C++. Numerical analysis in Rust could compete with Fortran in performance, but I don't know if any of that has been actualized in Rust yet.
Re:How fast can we make interpreted Python? (2013) by viperscape on Monday April 18, 2016 @05:51PM (#11523414)
I think some of that might start to come along with increase in compiler plugins, which is feature gated to nightly build right now.
Re:How fast can we make interpreted Python? (2013) by hardwaresofton on Monday April 18, 2016 @04:10PM (#11522805)
By what measurement?

I think the only thing I could say would be that it would be safer? And possible terser and possibly easy to understand.