hechang1997

While this cannot compile C/C++, it can serve as a fil-C alternative for unsafe pure rust code.

https://news.ycombinator.com/item?id=49284966

It’s easy to forget because it’s a fabricated perspective. Islamic/Arabian conquest of MENA isn’t really that different from what Romans or Persians did. That region is literally the source of human civilization (in the Old World at least) and had seen empires come and go ever since the Bronze Age, and along with them all sorts of cultures and religions. What fundamentally changed the dynamics of the region is not the islamic conquest but the shift of the center of the global trade away from Middle East and the Mediterranean to the Western Europe.

Here's the resort in question.

I quite like this though. All other expression based languages like MLs and Haskell use indentation, making it very hard to parse. To me, Rust's syntax allows very granular control. I wish more things in the language can become expressions, like the let expression, for/while loop.

A subtle point often missed is that if you want the anonymous structure of your closure itself to own a value, so that you can have a closure with a `'static` lifetime (which lives forever) that still could be called multiple times, you must use move keyword. If you just move the values into the closure manually, your closure will be a `FnOnce` since the compiler will mistakenly believe that you want to move that value each time the closure gets invoked, which can only happen once if the moved value doesn't implement `Copy`. In constrast, if you use the `move` keyword, compiler will correctly move the value into the anonymous structure of the closure itself during its construction, and the closure will be a `FuMut` and/or `Fn` as long as you don't consume the said value in the closure.

> And the risk of people abusing power to advance their personal agenda is NOT something that would get passed easily once discovered.

Yes, it is. It get discovered all the time and no one gives a sh*t about it.