Lol, it took me a while to realize it's the compiler essentially saying "how high".
126 1 ReplyI do enjoy the rust compiler error messages. They are nicely formatted
69 0 ReplyI'm trying to learn rust and so far this has definitely made it so much more accessible.
Not to mention their super useful "rustlings" training which has these nice little challenges to get you used to language and syntax
21 0 Reply
That's what makes us humans different from computers. We don't ask how high, we just do it. Now, if it were a C pointer it would jump anywhere from 0 to 2^32-1. That's why C is more suited for artificial intelligence than it might initially seem. Thanks for coming to my tedx talk
48 2 ReplyPointers are ackshully 48 bits on amd64 (which is most PCs and servers)
6 0 ReplyI was mostly joking about a stray pointer of type uint32_t*
So the size of the pointer itself doesn't matter
5 0 ReplyWell ackshully newer CPUs support 5-level-paging which uses 56 bits.
5 0 Reply
i dislike rust, but have to give them credit for helpful error messages. not quite racket level but impressive
37 0 ReplyWhat made you dislike it?
5 0 Replythe syntax.
3 0 Reply
WRONG, PRIVATE!
Now drop and give me int(ceil(19.9))!
32 0 ReplyHeight should be a float
13 3 ReplyI don't know Rust but jump typically moves the program counter, where the height represents the number of instructions to move
10 1 ReplyAfaik rust doesn't have functions like that as they lead to unsafe code that's impossible to check variable lifetimes for. I think OP created the jump function.
14 0 Reply
It's height in centimeters
6 0 ReplyChad quantised rust
4 0 ReplyNever use floats.
1 0 ReplyBut then wouldn't it be
fly(height: f64)
instead ofjump(height: i32)
?1 0 Reply
Huh, usually they ask 'jump where?'
3 0 Reply