Let

>let

>compiler error
>it's because I wrote "let" and not "let rec"

>def
>dim
>fi
>wend

...

letlets begone

>ifndef

>why is there mathematics in my code REEEEEEEEEEE

Why are languages make different keywords for mutable and immutable? Isn't the compiler smart enough to see that the variable never gets changed?

There are many layers of indirection a compiler can't predict and it's better to not make automatic assumptions about the code or else it becomes a mushy mess of hidden "optimizations" the user can't predict.

let rec op_is = function
OP -> brainlet
| _ -> op_is OP

>static inline const void

>being a letlet

>fn

>proc

>using arbitrary/random letters for functions
Is this some kind of requisite in order to write GNU software?

>const void
That makes no sense

local

It's to stop the programmer accidentally changing something that should not be changed.

disgusting

>the body hit the floor

that was all i needed to know about rust. as soon as i saw "let" i knew the devs where children.

>That makes no sense

Welcome to C++

>exam on functional programming
>decided to write a for loop wrapper and passed everything into it