Casey Rodarmor

Variables can depend on dotenv variables, regardless of whether they're redefined, since they can use env variables, so I don't think this is possible in general. I'll leave it open...

Great thought, @laniakea64! I think this should be pretty simple. I'd just make it `setting(name)`. In particular, `name` can be a keyword token. If anyone wants to take a crack...

Thanks for the report! I'd be fine if someone created a PR supporting this, although it might, in practice, be quite a messy PR. `imdl` relies on serde for serializing...

I think maybe the best way to support this would be to have a `fix` command, which could fix common problems with torrents, and avoids using serde. I.e., it uses...

I think this would just be too complex for the implementation. `imdl` uses `serde`, and I can't think of a simple way to substitute values from `.utf-8` keys when they...

Sweet, good to hear!

This seems pretty reasonable to me. And actually, I think this already works with the alias attribute, in progress in #2615. I think actually we could consider just disabling an...

Just tried this locally, and it seems like a nice addition! I was able to rewrite this: ```rust memoized_await( (), |()| async { Api::default() .packages() .await .unwrap() .into_iter() .collect::() },...

One thought, is it necessary to give `await_once` access to the initial state? Instead of: ```rust await_once( |state| async { async_function(state).await }, |state: &mut State, output| state.foo = output, ),...

Actually, thinking more about it, I think requiring a function/closure which takes the current state and returns a future is perhaps best for clarity, i.e., reinforcing that the closure will...