bare4_3

examples/bare4.rs

@@ -127,16 +127,16 @@ fn main() -> ! {
 //
 //    Why is it important that ordering of volatile operations are ensured by the compiler?
 //
-//    ** your answer here **
+//    Since some operations has to be executed before others.
 //
 //    Give an example in the above code, where reordering might make things go horribly wrong
 //    (hint, accessing a peripheral not being powered...)
 //
-//    ** your answer here **
+//    If we swap row 59-60 with 63-64, then we wont get the nice blinking anymore.
 //
 //    Without the non-reording proprety of `write_volatile/read_volatile` could that happen in theory
 //    (argue from the point of data dependencies).
 //
-//    ** your answer here **
+//    Writing/Reading in wrong order may end up in unexpexed results
 //
 //    Commit your answers (bare4_3)