solana VS rust

Solana (9700 GitHub Stars) https://github.com/solana-labs/solana

EIP Core standards: Changes to Solana’s core code go through “feature gates” in the Solana repo. Yes, it’s much less organized than the EIP pages you are used to, and a headache to understand or keep up with. A cost of the speed of development, I’m told.

I visited the project on github (https://github.com/solana-labs/solana), and tried to get an overview of the ~800 open issues and ~100 open PRs.

Solana

With the introduction of new and advanced blockchain platforms in the Web 3.0 scene, the narrative around Ethereum has slowly shifted towards its younger “Ethereum Alternatives”. Solana, Avalanche, and MultiversX (former Elrond) are some of the crypto blockchains that are given this terminology, as they share similar features but are comparatively cheaper and better than Ethereum.

I understand this initiative is connected with Solana network [1] in some way?

[1] https://solana.com/

They do, actually: https://github.com/solana-labs/solana/security/policy

Not sure I understand your question, but if you want the source code you can find it on github (https://github.com/solana-labs/solana)

Some topics that may be discussed in the next call include @ShinobiSystems Timely Vote Credits proposal (https://github.com/solana-labs/solana/blob/master/docs/src/proposals/timely-vote-credits.md), @elusivprivacy new built-in cryptographic operations to accelerate ZK verification (for privacy tech), and feature activation coordination standards.

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.