ziglings VS nrf-hal

Master syntax - language possibilities, so that you can read code. Ziglings (or github) does great job teaching it!

I am interested to learn, how Traits in Rust and Interfaces in Go behave differently from this concept.

[1] https://github.com/ratfactor/ziglings/blob/main/exercises/09...

Is Zero the space lizard (dinosaur?) with the hammer in the picture in Ziglings' readme? (I like this guy)

Yesterday someone introduced me to ziglings, do you mean that? https://github.com/ratfactor/ziglings/tree/main/exercises

Hi! I am learning zig through the Ziglings repo. I was messing around exercise 54 where it shows how you can create a pointer to many items instead of a slice:

Also, https://github.com/ratfactor/ziglings if you missed it.

Along with ziglearn, I also found ziglings useful.

You should try again. I think that code is verbose because of the borrowing and because you're trying to do a one-liner. I use the nrf-hal library with the nrf52840, and the code reads pretty nicely. Here's an example:

https://github.com/nrf-rs/nrf-hal/blob/master/examples/blink...

Reading nrf-hal source, unfortunately new does re-configure the UARTE, and there is not a new_unchecked. The solution I can think of is to duplicate the write code with nrf52833_hal::pac::UARTE0. The Uarte type does not contain any metadata, it exists purely to guard the init of UARTE.

Really good. Check out the examples in the nrf-hal repo. Also, if you don't mind forking out for some extra components the Knurling sessions by Ferrous Systems are ace.

The embedded HAL crates do this with extensive use of macros, for example: https://github.com/nrf-rs/nrf-hal/blob/aae17943efc24baffe30b...

This solution makes sense given the constraints of Rust, but there's quite a cost in terms of compiler time and cognitive overhead to understand what is going on.

(Aside: I didn't use the HAL in my Rust firmware, that's a higher layer of abstraction; I only used the PAC crates.)