Yup, that does it. Fuck Rust.
I just tried to write a simple function that takes an integer and returns that integer divided by 3. It failed and then I got back to Python 2.7 and, in 10 minutes, was able to write an equivalent and actually useful function. So fuck you Rust, and your "borrow checker" that took 20 minutes to figure out what to do and then 3 minutes to actually execute. Fuck you, and your promise of "zero runtime". In practice, you have 10x the runtime of a real world program to actually make it perform well. Fuck you. You can't even do the easy stuff right.
What is the point of writing your own programming language if you can't even get the simplest of things right?
>getting filtered this hard by trannylang
The absolute state of pyhtooners
This better be bait. How could it take you 10 minutes to write return n/3?
works on my machine
you're missing a return statement there buddy
why would I include it when it's not necessary?
Jesus Christ
retard
Most knowledgeable rust critic
>fuck this retarded zoomer language
>I'm going back to my other retarded zoomer language
>I just tried to write a simple function that takes an integer and returns that integer divided by 3. It failed
Holy kek. Please for the love of god show us the retarded code you wrote when trying and failing to divide a fucking number.
>I got back to Python 2.7 and, in 10 minutes,
you went too far with the bait there
python still probably faster than rust.. sad
Lolwtf
I didn't know you could approximate Fibonacci in O(1) with such precision
Well obviously because the golden ratio is approximated by n/n-1 of the Fibonacci sequence.
you can do that with any linear recurrence relation. write it down as a matrix, multiply it with itself and compute the limit of that.
>pow
>O(1)
have you taken a look at the compiler output for the C version? I bet you the compiler knew what you were doing >.>
>comparing the runtime of two different algorithms
>in 10 minutes
Good job quoting one of the several obvious pieces of bait in that post
it took you 10 minutes to write
def divide3(x:int)->int:
return x//3
?
>no unit test
>no docstring
>no comments
>no entry in the changelog
sorry, but we can't accept your new feature like this. I'm afraid we have to reject this until you meet our coding standards.
Those are objectivelt great things. Trying to maintain untested garbage is a nightmare