FAQ gathering for rust-embeeded.org

[trappitsch]

As discussed during the archeology day (#49), the FAQs are a bit outdated and in need of editing. This discussion shall serve to gather FAQs (and hopefully good answers for them) that we can then use to update the website.

If you came across frequently asked questions that would be a great fit for the rust-embeeded.org website, please post them here by adding a new comment. It would of course also be great if you can/would draft a response for this FAQ! Additional responses/edits/etc. can be drafter for each question using the reply-to-this-comment feature.

Once we have a nice list together, I will start putting them together in some decent looking formatting and prepare a draft PR for review for the website!

[trappitsch]

Question that came up in the Matrix chat here and there and that might be good to point to:

How can I guarantee that my program is memory-safe in case of a stack overflow?

[trappitsch]

Should have a quick discussion on stack layout, how a program with can corrupt static variables when the stack grows too large and grows into the static section. The solution would be using flip-link to invert the stack, i.e., such that static variables are defined on top and then the stack grows below downwards. Thus, a stack overflow will result in a hard-fault instead of silent data corruption.