>Immutability ends where you stop interacting with I/O
>Entire callstack relies on remote operation to return successfully to preserve immutability
>Boundary between immutable and mutable logic is handwavey and quietly swept under the rug
This is what you faggots actually believe.
Let mut x = 3;
Ryder Wood
Alexander Richardson
I think hes on and about some of that BBC
Jacob Carter
You forgot weak_ptr, malloc and free.
Protip: modern C++ puts emphasis on using stack for 99.9% of everything.
Joshua Williams
>I/0
That tickles my autism
Asher Foster
>Entire callstack relies on remote operation to return successfully to preserve immutability
It relies on the foreign code to not trash random memory, yes. Library calls in C rely on the same thing.
>Boundary between immutable and mutable logic is handwavey and quietly swept under the rug
You've never heard of Haskell, I take it?
Ian Roberts
>I'm used to explicitly saying a value is constant, therefor any language that explicitly says a value is mutable is cuck
Damn Jow Forums is retarded
Wyatt Gutierrez
Why not
let x=0;
mut y=0;
Why the verbosity.
Kayden Perry
It literally cucks your variables into submission.
Leo Baker
>Being this inefficient
Shiggy
Kayden Green
>Protip: modern C++ puts emphasis on using stack for 99.9% of everything.
If you have a lot of data it's a bad idea. Stack is very small.