16:30:00 <m-relay> <s​needlewoods:monero.social> I noted `sweep_unmixable`/`sweep_dust` commands (from wallet-cli/wallet-rpc) do _not_ have a `priority` option, while all other `sweep_*` and `transfer*` commands do have that option, maybe I'm missing something and there is a reason for that, or is it just rarely used and no one complained so far?
16:30:01 <m-relay> <s​needlewoods:monero.social> Does anyone think it would make sense to add the priority option to `wallet2::create_unmixable_sweep_transactions()` and then to CLI and RPC? Currently it uses hard coded priority 1 ([src](https://github.com/monero-project/monero/blob/a4a4a1df1d8b15f804645be73206277de6091260/src/wallet/wallet2.cpp#L11777)).
16:59:06 <m-relay> <j​effro256:monero.social> I think the latter reason. `sweep_unmixable` is kind of a niche command that is still the only way to make v1 txs
16:59:45 <m-relay> <j​effro256:monero.social> I don't think it'll be very useful in the context of FCMP++ since all the anonymity pools are merged, so nothing is "unmixable"
17:00:24 <m-relay> <j​effro256:monero.social> I don't think it's worth trying to update `create_unmixable_sweep_transactions()` or add it to the new API IMO