From 57e4a1764c5229fe376e80ef27a04d305693e311 Mon Sep 17 00:00:00 2001
From: Blinningjr <nicke.l@telia.com>
Date: Fri, 4 Dec 2020 15:34:35 +0100
Subject: [PATCH] Finished timing_resources

---
 examples/timing_resources.rs | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/examples/timing_resources.rs b/examples/timing_resources.rs
index 67dde0c..acddcbc 100644
--- a/examples/timing_resources.rs
+++ b/examples/timing_resources.rs
@@ -321,4 +321,10 @@ const APP: () = {
 // (Hint, what possible optimization can safely be applied by RTIC + Rust + LLVM.)
 //
 // [Your answer here]
-// TODO
+// From the exercises I have learnt that the RTIC way of handling concurrency is much faster
+// because it doesn't have to use locks everywhere. And the lock are much more efficient then the
+// ones used in C. RTIC is also much more efficient regarding context switching because it doesn't do it as often.
+// Rust provides safety for pointers which C doesn't. This means that it is easier to write shorter
+// code in rust, which also can be easily more optimized compared to C. The optimizer for C can
+// also be much more aggressive resulting in code that doesn't work as intended.
+//
-- 
GitLab