rust VS polkadot

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.

Polkadot (6400 GitHub Stars) https://github.com/paritytech/polkadot

I don't think asynchronous backing has any direct effect on the number of parachains, no (I mean, there likely is an effect, but it's not the goal and my understanding is that any effect on that would be minimal, although I'm not involved in the deep engineering here). It increases throughput, correct, by decreasing the time between blocks by not needing to do a "roundtrip" to the relay chain to build new blocks. See https://github.com/paritytech/polkadot/issues/3779 for an overview.

"The 27 waiting day is unavoidable and a very important security measure to protect against certain attacks and vulnerabilities of PoS. I totally understand that it is annoying, but arguably it is for the benefit+security of the overall network, which includes you as well at the end of the day as DOT-holder." - from this GitHub discussion.

Ref: Kianenigma @ https://github.com/paritytech/polkadot/issues/2418

Polkadot 0.9.37 has been released with MEDIUM upgrade priority. https://github.com/paritytech/polkadot/releases/tag/v0.9.37

Specifically, it was this PR that changed it: https://github.com/paritytech/polkadot/pull/6230

Actually it looks like you can! It's just not recommended. This is from the official documentation: "Starting with runtime version v23 natively included in the client version 0.8.23, payouts can go to any custom address. If you'd like to redirect payments to an account that is neither the controller nor the stash account, set one up. Note that setting an exchange address as the recipient of the staking rewards is extremely unsafe.*

A particular validator sent out a LOT of dispute reports (i.e., saying that other validators did something incorrectly) last night (for reasons unknown). It looks like other nodes "choked" reading all of these disputes, and one subsystem died, stalling nodes but NOT killing the process. It's still being investigated, but you can look at the issue on Github to see it being discussed here: https://github.com/paritytech/polkadot/issues/6412