-
-
Notifications
You must be signed in to change notification settings - Fork 170
doc: Talk about Documentation Organization/Overview [doc: 5/N] #1293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -69,13 +69,34 @@ | |
//! The minimum supported Rust version is currently 1.70. | ||
//! Our policy is to support at least the past two stable releases. | ||
//! | ||
//! # Crate organisation | ||
//! # API/User Documentation, Documentation Structure, and other Resources | ||
//! | ||
//! Down below, you find typical technical documentation of all types, modules, | ||
//! and functions exported by `uefi`. | ||
//! | ||
//! For a TL;DR quick start with an example on how to create your own EFI | ||
//! application, please check out [the UEFI application template][template]. The | ||
//! [Rust UEFI Book] is a more beginner-friendly tutorial with How-Tos, and | ||
//! overviews of some important UEFI concepts and the abstractions provided by | ||
//! this library. | ||
//! | ||
//! For more details of UEFI itself, see the latest [UEFI Specification][spec]. | ||
//! | ||
//! # Library Structure & Tips | ||
//! | ||
//! The top-level module contains some of the most used types and macros, | ||
//! including the [`Handle`] and [`Result`] types, the [`CStr16`] and | ||
//! [`CString16`] types for working with UCS-2 strings, and the [`entry`] and | ||
//! [`guid`] macros. | ||
//! | ||
//! ## UEFI Strings | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We never talked about this here specifically, but I think it is important. |
||
//! | ||
//! Rust string literals are UTF-8 encoded and thus, not compatible with most | ||
//! UEFI interfaces. We provide [`CStr16`] and [`CString16`] for proper working | ||
//! with UCS-2 strings, including various transformation functions from standard | ||
//! Rust strings. You can use [`ctr16!`] to create UCS-2 string literals at | ||
//! compile time. | ||
//! | ||
//! ## Tables | ||
//! | ||
//! The [`SystemTable`] provides access to almost everything in UEFI. It comes | ||
|
@@ -186,10 +207,12 @@ | |
//! [`SystemTable`]: table::SystemTable | ||
//! [`r-efi`]: https://crates.io/crates/r-efi | ||
//! [`entry-macro`]: uefi_macros::entry | ||
//! [`ctr16!`]: crate::cstr16 | ||
//! [`unsafe_protocol`]: proto::unsafe_protocol | ||
//! [contributing]: https://github.com/rust-osdev/uefi-rs/blob/main/CONTRIBUTING.md | ||
//! [issue tracker]: https://github.com/rust-osdev/uefi-rs/issues | ||
//! [spec]: https://uefi.org/specifications | ||
//! [template]: https://github.com/rust-osdev/uefi-rs/tree/main/template | ||
//! [unstable features]: https://doc.rust-lang.org/unstable-book/ | ||
//! [rustc-uefi-std]: https://doc.rust-lang.org/nightly/rustc/platform-support/unknown-uefi.html | ||
//! [uefi-std-tr-issue]: https://github.com/rust-lang/rust/issues/100499 | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to add a small replacement in README.md in the next PR. But I want to keep this PR small