Nadrieril
Nadrieril
This would be getting off-topic, so I answered this [on Zulip](https://rust-lang.zulipchat.com/#narrow/stream/213817-t-lang/topic/Details.20of.20match.20guard.20semantics).
To your point @clarfonthey, my deref pattern emulation does lack exhaustiveness, and that is unfortunate. I think this is well worth the cost however. Quite generally, if-let guard patterns allow...
Allow me to get excited at the possibilities: ```rust fn foo(map: &mut HashMap) { match map { hashmap_mut!{ "x": x, "y": 42, .. } => *x += 1, // expands...
> Right now, matches are already pretty slow when they involve complex patterns, even though they can "in theory" be sped up more based upon all of the reordering I...
That really seems like a bug. See also #194 for our plans for closures
I would guess the tuple comes from the `Fn` trait: a closure like `|x, y, z| ...` implements `Fn`. Do we special-case the case of single arguments anywhere?
I fixed this in https://github.com/AeneasVerif/charon/pull/494. Now the closure signature matches the locals.
Indeed! Thanks for writing this down. And correspondingly in llbc these statements should get an extra `unwind: Block` field. Note that for `Assert` this may require updating some of our...
Drop was done in #893!
Note: rustc will complain about such an attribute because it will try to find a macro with that name. Adding ```rust #![feature(register_tool)] #![register_tool(charon)] ``` at the top of each file...