faq: Fix typo
This commit is contained in:
parent
b326ee19bb
commit
bb743420be
1 changed files with 4 additions and 2 deletions
|
@ -3,8 +3,10 @@
|
||||||
Over time, a couple of best practices have emerged. The following list should serve as a guideline for developers writing embedded software in _Rust_, especially in the context of the _Embassy_ framework.
|
Over time, a couple of best practices have emerged. The following list should serve as a guideline for developers writing embedded software in _Rust_, especially in the context of the _Embassy_ framework.
|
||||||
|
|
||||||
== Passing Buffers by Reference
|
== Passing Buffers by Reference
|
||||||
It may be tempting to pass arrays or wrappers, like link:https://docs.rs/heapless/latest/heapless/[`heapless::Vec`], to a function or return one just like you would with a `std::Vec`. However, in most embedded applications you don't want to spend ressources on an allocator and end up placing buffers on the stack.
|
It may be tempting to pass arrays or wrappers, like link:https://docs.rs/heapless/latest/heapless/[`heapless::Vec`],
|
||||||
This, however, can easily blow up your stack if you are not careful.
|
to a function or return one just like you would with a `std::Vec`. However, in most embedded applications you don't
|
||||||
|
want to spend resources on an allocator and end up placing buffers on the stack. This, however, can easily blow up
|
||||||
|
your stack if you are not careful.
|
||||||
|
|
||||||
Consider the following example:
|
Consider the following example:
|
||||||
[,rust]
|
[,rust]
|
||||||
|
|
Loading…
Reference in a new issue