Difference between revisions of "Rust"
(Update to present day situation: The pointer variety is gone and GC values aren't really used anymore.) |
(Remove note about 1.0 release pending (It's 1.12 now) & include some references) |
||
Line 14: | Line 14: | ||
Writing FFI bindings to C code is easy. The [https://crates.io/ Cargo] tool handles builds and dependencies to third-party packages. There is built-in unit test support. | Writing FFI bindings to C code is easy. The [https://crates.io/ Cargo] tool handles builds and dependencies to third-party packages. There is built-in unit test support. | ||
==Rust Roguelikes== | |||
*[https://github.com/dpc/rhex] rhex | |||
*[https://github.com/tomassedovic/roguelike-tutorial] Roguelike Tutorial, A port of the Complete Roguelike Tutorial, using python+libtcod. | |||
*[https://github.com/serprex/rg] rg, still in very early stages |
Revision as of 13:46, 10 October 2016
Rust | |
---|---|
Programming Language | |
Company | Mozilla |
Influences | C++, Erlang, Haskell, Standard ML |
Updated | 2014-11 (0.12) |
Status | Beta |
Licensing | Open Source (MIT License) |
Platforms | Linux, OS X, Windows, FreeBSD |
Official site of Rust |
Rust is a systems programming language from Mozilla Research. It is aiming to be a viable replacement for C++ and used by Mozilla to write a next-generation web browser engine. Unlike most high-level programming languages that use garbage collection, Rust uses the scope-delimited memory management idiom of C++ with stronger enforcement at language level. It uses an abstraction idiom similar to Haskell's type classes instead of OO, and supports reasonably extensive generic programming with type parameters that can be constrained to implemented traits. It has a macro system.
The language and type system have been designed to make it impossible to create memory leaks or null pointer references outside regions explicitly marked as unsafe, while maintaining C++-style explicit memory handling. The cost for this is a somewhat complex core language with various smart pointer types and explicit value lifetime annotations.
Writing FFI bindings to C code is easy. The Cargo tool handles builds and dependencies to third-party packages. There is built-in unit test support.