Rust: Difference between revisions

← Older edit

Rust (view source)

Revision as of 13:37, 7 June 2024

1,398 bytes added , 28 days ago

m

Reverted edits by Melina148 (talk) to last revision by Adavis07

[unchecked revision]

VisualWikitext

Anonymous user

osdev>Nightishaman

Revision as of 19:42, 11 May 2016 (view source) osdev>Ericson2314 (Add more libraries) ← Older edit		Latest revision as of 13:37, 7 June 2024 (view source) osdev>Nightishaman m (Reverted edits by Melina148 (talk) to last revision by Adavis07)
(27 intermediate revisions by 20 users not shown)
Line 1: '''Rust''' is a systems language sponsored by Mozilla, focused on three things: safety, speed, and concurrency. It accomplishes many of these goals through strong compile-time checks, allowing for very little overhead at runtime. Performance is comparable to C or C++, while being free of many of the problems caused by things like dangling pointers, buffer overflows, and iterator invalidation. While Rust is very much a "curly-brace" language, it also takes many cues from ML. Almost everything is an expression, and there is a very strong type system, including sum types and powerful generics. Rust provides a mechanism to subvert its safety checks when necessary, by adding an 'unsafe' annotation to portions of your code. This allows you full access to raw pointers, while controlling exactly how they are used. Often, Rust code that uses unsafe will do so as an implementation detail, allowing for them to expose a safe interface. Line 7: == Operating System Development == Rust has a comparable amount of runtime to C and C++, and has set up its standard library to be amenable towards OS development. Specifically, the standard library is(std) ~~split~~consists ~~into~~of two smaller parts: core and ~~std~~alloc. Core isconsists of the ~~lowest~~primitive, platform-~~level~~independent ~~aspects~~components ~~only,~~of ~~and~~the standard library. It doesn't include things like allocation, threading, and other higher-level features. Alloc is used for managing heap allocations, smart pointers, and simple data collections. Std builds on top of core and alloc to add ~~them~~other OS dependent features, such as files and processes. Using only core and alloc instead of std is as easy as adding anthe '''no_std''' annotation into your main source file. Every Rust compiler is a cross-compiler, which makes setup easier. ~~There are still some rough edges when doing OSDev, and they require using nightly-only features. These are currently being worked on.~~ == Active Projects == * [https://github.com/Andy-Python-Programmer/aero A mature POSIX OS] * [https://os.phil-opp.com/ "Writing an OS in Rust"] * [https://osblog.stephenmarz.com/ Tutorial: RISC-V OS using Rust] * [https://github.com/thepowersgang/rust-barebones-kernel Meaty Bare-Bones] * [https://github.com/~~thepowersgang~~skyzh/~~rust_os~~core-os-riscv ~~"Tifflin"~~core-os-riscv] An xv6-like operating system RISC-V based with multi-core support * [https://github.com/thepowersgang/rust_os Tifflin] Multiboot image for x86_64 has VFS and userland * [http://www.redox-os.org Redox] ** One of the largest and most active Rust OS projects * [https://~~github~~www.~~com/hackndev/zinc~~tockos.org ~~Zinc~~Tock] optimized for embedded devices uses libcore isolates drivers and applications targets embedded MCUs, ARM only so far * [http://intermezzos.github.io/ intermezzOS] Small kernel + book, specifically for learning OSDev through Rust on hiatus indefinitely * [https://github.com/ryanra/RustOS Ryanra's RustOS] ** Uses libcore/collections/alloc * [https://github.com/QuiltOS/QuiltOS QuiltOS] Forked from Ryanra's RustOS Main goal is demoing OS Dev libraries written in Rust. * [https://source.that.world/source/rux Rux] * [https://github.com/nebulet/nebulet Nebulet] ** Has an end goal of running [[WebAssembly]] in the kernel for a performance increase * [https://github.com/theseus-os/Theseus Theseus] ** An experimental OS written in Rust * [https://github.com/vinc/moros MOROS] ** A simple hobby OS with a text-based user interface == Past Projects == Rust went through a long and public development process, and used to have a significantly larger runtime. There were lots of experiments pre-1.0, ~~and so~~thus these projects are of historical interest, but ~~may~~aren't guaranteed to run or ~~not~~even build. * [https://github.com/charliesome/rustboot RustBoot] Line 40 ⟶ 55: * [https://github.com/Arcterus/kRnel kRnl] * [https://github.com/mahrz/rv6 rv6] * [https://github.com/hackndev/zinc Zinc] Line 45 ⟶ 61: * [https://github.com/gz/rust-x86 libx86]: Library to program x86 hardware. * [https://github.com/~~Tobba~~rust-osdev/~~libcpu~~x86_64 ~~libcpu~~x86_64]: Library to program ~~CPUs~~x86_64 hardware. * [https://github.com/rust-osdev/bootloader bootloader]: A rust bootloader. * <strike>[https://github.com/Tobba/libcpu libcpu]: Library to program CPUs.</strike> Now absorbed into libx86. * [https://github.com/gz/rust-slabmalloc slabmalloc]: Low-level memory allocator for liballoc. * [https://github.com/gz/rust-multiboot multiboot]: Library to read multiboot layout. * [https://github.com/mvdnes/~~spinlock~~spin-rs spin]: Various synchronization primitives implemented with spinning. Closely mimics `std::sync`'s interface. * [https://github.com/nathan7/libfringe fringe]: Context switching agnostic to how stacks are allocated. Line 60 ⟶ 78: * [http://os.phil-opp.com/ Blog Series: Writing an OS in Rust] * [http://www.randomhacks.net/2015/11/11/bare-metal-rust-custom-target-kernel-space/ Retarget your compiler so interrupts are not evil] * [[BOOTBOOT]] loader has an example 64 bit higher half kernel in Rust * [https://github.com/rust-osdev rust-osdev on GitHub] [[Category:Languages]]