I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result.
As a non-native speaker, it is hard for me to evaluate the finer details
of this, so let me know if you would like to see changes (or even
better:
make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
Bumps the patch group in /src/bare-metal/aps/examples with 2 updates:
arm-pl011-uart and [bitflags](https://github.com/bitflags/bitflags).
Updates `arm-pl011-uart` from 0.3.1 to 0.3.2
Updates `bitflags` from 2.9.1 to 2.9.3
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps the patch group in /src/exercises/bare-metal/rtc with 3 updates:
arm-gic, arm-pl011-uart and
[bitflags](https://github.com/bitflags/bitflags).
Updates `arm-gic` from 0.6.0 to 0.6.1
Updates `arm-pl011-uart` from 0.3.1 to 0.3.2
Updates `bitflags` from 2.9.1 to 2.9.3
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This section covers both references and slices, but the exercise focuses
on references. This speaker note briefly discusses the option to use
slices instead, and a cost of doing so.
Bumps the minor group in /src/bare-metal/aps/examples with 1 update:
[aarch64-paging](https://github.com/google/aarch64-paging).
Updates `aarch64-paging` from 0.9.1 to 0.10.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/google/aarch64-paging/releases">aarch64-paging's
releases</a>.</em></p>
<blockquote>
<h2>0.10.0</h2>
<h2>New features</h2>
<ul>
<li>Added <code>Attributes::GP</code> bit for BTI guarded pages.</li>
</ul>
<h2>Breaking changes</h2>
<ul>
<li><code>zerocopy</code> feature has been removed.
<code>PageTable::write_to</code> is provided instead.</li>
<li><code>IdMap::activate</code> now returns the previous TTBR value
rather than storing it, and
<code>IdMap::deactivate</code> takes the TTBR value to restore as a
parameter. <code>IdMap::mark_active</code> no longer
takes a previous TTBR value parameter. The same applies to the
equivalent methods on <code>LinearMap</code>.</li>
<li>Renamed <code>Mapping::activate_raw</code> to <code>activate</code>,
and added previous TTBR value parameter to
<code>Mapping::deactivate</code>.</li>
<li>A page table may be activated multiple times (e.g. on multiple
cores) and will keep track of how
many times it has been activated. It will only be considered inactive
once it has been deactivated
the same number of times.</li>
<li><code>MapError::PteUpdateFault</code> now contains a
<code>usize</code> rather than a <code>Descriptor</code>.</li>
<li><code>Descriptor</code> no longer implements <code>Copy</code>,
<code>Clone</code>, <code>Default</code>, <code>PartialEq</code> or
<code>Eq</code>, as it now
contains an <code>AtomicUsize</code> rather than just a
<code>usize</code>. Various methods on <code>Descriptor</code> now take
<code>&self</code> rather than <code>self</code>.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/google/aarch64-paging/blob/main/CHANGELOG.md">aarch64-paging's
changelog</a>.</em></p>
<blockquote>
<h2>0.10.0</h2>
<h3>New features</h3>
<ul>
<li>Added <code>Attributes::GP</code> bit for BTI guarded pages.</li>
</ul>
<h3>Breaking changes</h3>
<ul>
<li><code>zerocopy</code> feature has been removed.
<code>PageTable::write_to</code> is provided instead.</li>
<li><code>IdMap::activate</code> now returns the previous TTBR value
rather than storing it, and
<code>IdMap::deactivate</code> takes the TTBR value to restore as a
parameter. <code>IdMap::mark_active</code> no longer
takes a previous TTBR value parameter. The same applies to the
equivalent methods on <code>LinearMap</code>.</li>
<li>Renamed <code>Mapping::activate_raw</code> to <code>activate</code>,
and added previous TTBR value parameter to
<code>Mapping::deactivate</code>.</li>
<li>A page table may be activated multiple times (e.g. on multiple
cores) and will keep track of how
many times it has been activated. It will only be considered inactive
once it has been deactivated
the same number of times.</li>
<li><code>MapError::PteUpdateFault</code> now contains a
<code>usize</code> rather than a <code>Descriptor</code>.</li>
<li><code>Descriptor</code> no longer implements <code>Copy</code>,
<code>Clone</code>, <code>Default</code>, <code>PartialEq</code> or
<code>Eq</code>, as it now
contains an <code>AtomicUsize</code> rather than just a
<code>usize</code>. Various methods on <code>Descriptor</code> now take
<code>&self</code> rather than <code>self</code>.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="3aa97a9233"><code>3aa97a9</code></a>
Prepare for 0.10.0 release.</li>
<li><a
href="426f0eb2b8"><code>426f0eb</code></a>
Add changes to changelog. (<a
href="https://redirect.github.com/google/aarch64-paging/issues/81">#81</a>)</li>
<li><a
href="3046d1f8ba"><code>3046d1f</code></a>
Add changes to changelog.</li>
<li><a
href="ffaefdd6eb"><code>ffaefdd</code></a>
Add support for GP bit (<a
href="https://redirect.github.com/google/aarch64-paging/issues/80">#80</a>)</li>
<li><a
href="f7073ed3ef"><code>f7073ed</code></a>
Bump bitflags from 2.9.0 to 2.9.1 (<a
href="https://redirect.github.com/google/aarch64-paging/issues/78">#78</a>)</li>
<li><a
href="3146fc9472"><code>3146fc9</code></a>
Deal with memory ordering in page tables</li>
<li><a
href="83c51b4006"><code>83c51b4</code></a>
Drop dependency on zerocopy</li>
<li><a
href="73cf4deb34"><code>73cf4de</code></a>
Mark page tables active before loading them into the MMU</li>
<li><a
href="c58a108b2e"><code>c58a108</code></a>
Move TTBR preserve/restore out of the API</li>
<li><a
href="0d3a2d6339"><code>0d3a2d6</code></a>
Revert "Factor out Mapping::activate_raw."</li>
<li>Additional commits viewable in <a
href="https://github.com/google/aarch64-paging/compare/0.9.1...0.10.0">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps the patch group in /src/exercises/bare-metal/rtc with 1 update:
[aarch64-rt](https://github.com/google/aarch64-rt).
Updates `aarch64-rt` from 0.2.1 to 0.2.2
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/google/aarch64-rt/blob/main/CHANGELOG.md">aarch64-rt's
changelog</a>.</em></p>
<blockquote>
<h2>0.2.2</h2>
<h3>Improvements</h3>
<ul>
<li>Added optional parameters to <code>initial_pagetable!</code> to
allow initial MAIR, TCR and SCTLR values to
be specified. The default values are exposed as constants.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="2ba1c5153b"><code>2ba1c51</code></a>
Prepare for 0.2.2 release.</li>
<li><a
href="02b0802d0a"><code>02b0802</code></a>
Merge pull request <a
href="https://redirect.github.com/google/aarch64-rt/issues/17">#17</a>
from google/pagetable</li>
<li><a
href="442899cec7"><code>442899c</code></a>
Specify MAIR in example.</li>
<li><a
href="141090a51c"><code>141090a</code></a>
Allow just MAIR to be specified.</li>
<li><a
href="5720896eee"><code>5720896</code></a>
Allow initial MAIR, TCR and SCTLR values to be specified.</li>
<li><a
href="76b1699a3d"><code>76b1699</code></a>
Bump smccc from 0.2.1 to 0.2.2 (<a
href="https://redirect.github.com/google/aarch64-rt/issues/16">#16</a>)</li>
<li>See full diff in <a
href="https://github.com/google/aarch64-rt/compare/0.2.1...0.2.2">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Given
```
#[rustfmt::skip]
fn main() {
let input = '1';
match input {
key if key.is_lowercase() => println!("Lowercase: {key}"),
'q' => println!("Quitting"),
'a' | 's' | 'w' | 'd' => println!("Moving around"),
'0'..='9' => println!("Number input"),
_ => println!("Something else"),
}
}
```
the output will be
```
Number input
```
So in practice, failing the condition does result to the other arms if
the other arms are after that (if I'm reading this correctly).
These dependencies turned out not to be necessary, since depending on
the generated `com.example.birthdayservice-rust` also exports the common
binder functionality.
Adds the start of an unsafe deep dive to Comprehensive Rust.
The `unsafe` keyword is easy to type, but hard to master. When used
appropriately, it forms a useful and indeed essential part of the Rust
programming language.
By the end of this deep dive, you'll know how to work with `unsafe` code,
review others' changes that include the `unsafe` keyword, and produce
your own.
What you'll learn:
- What the terms undefined behavior, soundness, and safety mean
- Why the `unsafe` keyword exists in the Rust language
- How to write your own code using `unsafe` safely
- How to review `unsafe` code
Here is a tentative outline of a 10h (2 day) treatment:
Day 1: Using and Reviewing Unsafe
- Welcome
- Motivations: explain why the `unsafe` keyword exists
- Foundations: provide background knowledge; what is soundness? what is
undefined behavior? what is validity in respect to pointers?
- Mechanics: what a safe `unsafe` block should look like
- Representations and Interoperability: explore how data is laid out in
memory and how that can be sent across the wire and/or stored on disk.
- Reviewing unsafe
- Patterns for safer unsafe: Encapsulating unsafe code in safe-to-use
abstractions, such as marking a type's constructor as `unsafe` so that
invariants only need to be enforced once by the programmer.
Day 2: Deploying Unsafe to Build Abstractions
- Welcome
- Validity in detail: A refresher. Emphasis on the details of the
invariants that are being upheld by a “typical” unsafe block, such as
aliasing, alignment, data validity, padding.
- Concurrency and thread safety: understanding `Send` and `Sync`,
knowing how to implement them on a user-defined type
- Case study: Small string optimization
- Case study: Zero-copy parsing
- Review
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
This has a lot of detailed and high-quality API advice.
I think it's particularly useful to developers experienced in other
languages, who may default to carrying over design idioms where Rust has
better options.
This PR introduces:
- A new section for the "Idiomatic Rust" learning module
- (The beginning of) the section on newtype patterns
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
Now that there is a `rustup` package, we can take away the scary
language and ask people to install that. This has the advantage that
people get a trusted tool to download the latest Rust compiler.
The point at which the generics segment will be covered has changed
multiple times. After the last change, the 'logger trait' section was
not updated to reflect when it will now be covered. To keep it more
general, I suggest not specifying when it will be covered.
