no-std
Here are 221 public repositories matching this topic...
-
Updated
Jul 29, 2020 - Rust
-
Updated
Nov 19, 2020 - Rust
-
Updated
Nov 9, 2020 - Rust
-
Updated
Nov 14, 2020 - Rust
Currently the link layer will abort the connection when it does not receive the initial connect event:
This shouldn't happen. Instead, we should do what the comment suggests (and check it against the spec).
The effect of this bug is that establishing a connection
-
Updated
Oct 4, 2020 - Rust
-
Updated
Nov 21, 2020 - Rust
-
Updated
Oct 2, 2020 - C++
-
Updated
Feb 24, 2020 - Rust
-
Updated
Nov 21, 2020 - Rust
-
Updated
Oct 17, 2020 - Rust
-
Updated
Sep 9, 2020 - Rust
-
Updated
Oct 24, 2019 - Rust
-
Updated
Apr 20, 2020 - Rust
At the moment, the X86_64CoreRegs::regs field and X86[_64]CoreRegs::segments fields rely on an implicit ordering documented in their respective comments. It would be much better if explicit fields were used instead.
As pointed out in daniel5151/gdbstub#34 (comment), there is no "one true" ordering for these registers, which could result in some nasty bug
Improve this page
Add a description, image, and links to the no-std topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the no-std topic, visit your repo's landing page and select "manage topics."
The docs for
DrawTargetExtcurrently only contain examples for the individual sub draw targets. These examples don't demonstrate how multiple sub draw targets can be combined. An example forClipped<Translated<_>>should be added to theDrawTargetExtdocumentation.Additionally a simulator example should be added, which demonstrates the individual sub draw targets, but also useful combina