flip111

Let's say i want to manually load (include/require) this class https://github.com/symfony/var-dumper/blob/master/Dumper/HtmlDumper.php how would i refer to that file? Or rather how would i refer to that class now that it...

> setting multiple references for a single name does not make sense @stof please motivate your answer, i shall edit the first post to motivate my PR

@stof i agree with what you are saying. However i was too afraid to adjust more code then i already have and come up with new names for "reference". Anyway...

Similar situation here https://rust-embedded.github.io/book/start/qemu.html#a-non-standard-rust-program

Similar https://rust-embedded.github.io/book/start/qemu.html#running this one is even stranger because > For convenience here's the source code of src/main.rs: > cat examples/hello.rs Am i supposed to replace the source code of `src/main.rs`...

I will wait for the close or merge of https://github.com/rust-embedded/book/pull/169 before re-considering this.

> Always use volatile methods to read or write to peripheral memory, as it can change at any time In previous section of book it says: > . In C,...

> In software, we should be able to share any number of read-only accesses to these peripherals No idea what this means. Both from logically reading the sentence (on an...

> If some software should have read-write access to a peripheral, it should hold the only reference to that peripheral book makes a too big step how we go from...

> Well, luckliy in the hardware, there is only one instance of any given peripheral I think "instance" is used as a software term here. Which is strange because it's...