TrumpScript VS rust

One of rewrited PL, same shit like TrumpScript (https://github.com/samshadwell/TrumpScript), good practice for developers.

TrumpScript has the best error message: they are quotes directly taken from Trump himself.

format_args! is now part of the AST. https://github.com/rust-lang/rust/pull/106745

I've opened a PR to add format strings in Rust, I'd appreciate any feedback that anyone has: https://github.com/rust-lang/rust/pull/109647

"Experimental feature gate proposal interoperable_abi #105586"

As an engineer having spent most of 2022 learning the Rust language, I was a little worried about the no_std side of embedded systems programming.

The reason we are providing our own hasher is that the default one relies on the sys crate which is platform dependent. Our platform being unsupported, the associated implementation either does nothing or fails.

Further down that GitHub issue, it mentions the problem has been fixed:

* https://github.com/rust-lang/rust/issues/71871#issuecomment-...

* https://github.com/rust-lang/rust/pull/79998

Weirdly though, there's another issue (opened prior) that's ongoing and seems to indicate things aren't fixed after all:

* https://github.com/rustwasm/team/issues/291

>wasm32-unknown-unknown has an ABI incompatibility which means you cannot interoperate between C compiled to Wasm and Rust compiled to Wasm.

Since I was surprised to learn this, and to save everyone else the search, it's https://github.com/rust-lang/rust/issues/71871

Beyond that, it can also be really useful for catching bugs due to incorrect assumptions, just like with map seeding. That's why Rust now has -Zrandomize-layout to catch cases where code assumed that a Rust struct had a particular layout or even that any two different structs had the same layout.

The reasoning behind this is that if there are no more strong references but weak references still exist, the weak references need to refer back to the same memory, which won't be possible if the memory has already been freed. A bit counter intuitive and I got amazed when I first learned it. If you're interested in the details, check out the source code.

There's no magic behind Stdout. It is just like writing bytes into files and any types that implement std::io::Write playground. RawTerminal is merely a wrapper for Stdout, and Stdout is an empty struct that implements io::Write that calls a libc function that displays the written bytes to our terminal.