Analysis of information sources in references of the Wikipedia article "راست (زبان برنامهنویسی)" in Persian language version.
GH: A lot of obvious good ideas, known and loved in other languages, haven't made it into widely-used systems languages... There were a lot of good competitors in the late 70s and early 80s in that space, and I wanted to revive some of their ideas and give them another go, on the theory that circumstances have changed: the internet is highly concurrent and highly security-conscious, so the design-tradeoffs that always favor C and C++ (for example) have been shifting.
{{cite web}}: |first= missing |last= (help)After that last change fixing the logging scope context bug, looks like stage1/rustc builds. Just shy of midnight :)
… It’s impossible to be “as fast as C” in all cases while remaining safe… C++ allows all sorts of low-level tricks, mostly involving circumventing the type system, that offer practically unlimited avenues for optimization. In practice, though, C++ programmers restrict themselves to a few tools for the vast majority of the code they write, including stack-allocated variables owned by one function and passed by alias, uniquely owned objects (often used withauto_ptror the C++0xunique_ptr), and reference counting viashared_ptror COM. One of the goals of Rust’s type system is to support these patterns exactly as C++ does, but to enforce their safe usage. In this way, the goal is to be competitive with the vast majority of idiomatic C++ in performance, while remaining memory-safe…
At Mozilla Summit 2010, we launched Rust, a new programming language motivated by safety and concurrency for parallel hardware, the “manycore” future which is upon us.
|تاریخ= را بررسی کنید (کمک)After that last change fixing the logging scope context bug, looks like stage1/rustc builds. Just shy of midnight :)