Henrik Lievonen

> Is there any reason in your `update.sh` you have each peripheral's address range spelled out, instead of just putting 0x40000000-0x40070000, 0x50200000-0x50204000, 0x50300000-0x50304000, 0x50400000-0x50404000? Not really, other than to show...

> Could you add an entry to the changelog for this, please? Sure, I'll add an entry with next batch of changes. > Also, I wonder if it's a bit...

I have described one possible implementation for this in [a comment elsewhere](https://github.com/rp-rs/rp-hal/pull/143#issuecomment-930070759), but I don't know how to gate that for specific registers or peripherals only. I tried to look...

That would be unfortunate, but at least it would work. By the way, I have a POC available in [my fork](https://github.com/henkkuli/svd2rust/tree/rp2040-atomic-poc) if someone wants to take a look. Would something...

@teohhanhui @fdehau What would you think of adding a method `index_of_item_at(&self, point: (u16, u16), area: Rect, state: ListState) -> Option` for `List` that returns the index of the item at...

> @henkkuli There's already an `Index` trait in `core` / `std`. Sorry, I don't follow what you mean by this? There is [`std::ops::Index`](https://doc.rust-lang.org/std/ops/trait.Index.html), but I don't see what it has...

Here's a new idea that allows the API to be safe and escaping by default, but also expressive and expandable if needed: Add a new trait `IntoHtmlText` that takes care...

And now that I think of it, `IntoHtmlText` should implement an API based on `fmt::Formatter` just like `Debug`, `Display` and `Render`. Though it should be different from `Render` in the...