hax Pre/post `&mut` argument: remove `future` in favor of `old`

~make the proc macro parse both ::hax_lib::_final and _final~
~detect if (locally) there is any name clash, and ask the user to use ::hax_lib::_final instead~

We chatted about that, and we'll adopt the style of Verus / Prusti / Rustc proposal: use old to refer to the old value, and otherwise that's the future value.

Jul 15 '24 15:07 W95Psp

This issue has been marked as stale due to a lack of activity for 60 days. If you believe this issue is still relevant, please provide an update or comment to keep it open. Otherwise, it will be closed in 7 days.

Sep 17 '24 01:09 github-actions[bot]

Still something we want, we need to schedule it before too much code is written in that style.

Sep 18 '24 07:09 W95Psp

This issue has been marked as stale due to a lack of activity for 60 days. If you believe this issue is still relevant, please provide an update or comment to keep it open. Otherwise, it will be closed in 7 days.

Nov 18 '24 02:11 github-actions[bot]

I'll bump priority for that one, it's still important to get that done soon.

Nov 18 '24 08:11 W95Psp