Andrew Dona-Couch -- GitHub drop ICE

Something makes me unhappy that these are not interchangeable in a suitable environment: - `{{ 42 | abs }}` - `{{ template_var | abs }}` - `{% let local_var =...

Post is a bit long, my apologies. Please stick with it, I get somewhere interesting by the end :). --- I've thought a bit more about this and something occurred...

Interesting angle, @msrd0. Though askama is a macro, it emits a trait implementation, so the code it's lowered to has to play by the rules of functions, not macros. I...

That's a nice idea @msrd0, and seems to go to the idea that all filters should be written to take their argument by reference (since that pattern will not compile...

I've been thinking about your latter two questions a lot, and came to roughly the same conclusion. I've been avoiding writing cs-based APIs for some things based on the (almost...

Or even: ```rust fn main(cs1: CriticalSection) -> ! { interrupt::free(|cs2| { interrupt::hypothetical_enable(cs1); some_mutex.lock(&cs2); }); // .. } ``` But maybe it would be a new privileged type, such as: ```rust...

Would this be too heavy-handed a solution? ```rust pub struct CriticalPrologue { type Target = CriticalSection; fn deref(&self) -> &Self::Target { &self.0 } } mod interrupt { pub fn free...

> When commenting out the bad main in your example, it still does not compile? Oh my, I really thought I had checked that. No wonder I was so confused...

From what I can tell, this is not possible to implement due to limitations in `embedded-hal`. The `OneShot` trait itself would be easy enough (just delegate to the correct port...

Correction: there has been movement in the API, but not in a direction that supports this usage. Ahead of an imminent 1.0 release, the `channel()` associated function has been removed...