From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Wolfgang Bumiller <w.bumiller@proxmox.com>
Subject: [pve-devel] [PATCH proxmox-firewall v4 08/18] use std::mem::take over drain()
Date: Fri, 15 Nov 2024 13:10:59 +0100 [thread overview]
Message-ID: <20241115121109.170200-9-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20241115121109.170200-1-s.hanreich@proxmox.com>
This is more efficient than draining and collecting the Vec. It also
fixes the respective clippy lint.
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
Reviewed-by: Wolfgang Bumiller <w.bumiller@proxmox.com>
---
proxmox-firewall/src/rule.rs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/proxmox-firewall/src/rule.rs b/proxmox-firewall/src/rule.rs
index 3b947f0..b20a9c5 100644
--- a/proxmox-firewall/src/rule.rs
+++ b/proxmox-firewall/src/rule.rs
@@ -764,7 +764,7 @@ impl ToNftRules for FwMacro {
fn to_nft_rules(&self, rules: &mut Vec<NftRule>, env: &NftRuleEnv) -> Result<(), Error> {
log::trace!("applying macro: {self:?}");
- let initial_rules: Vec<NftRule> = rules.drain(..).collect();
+ let initial_rules: Vec<NftRule> = std::mem::take(rules);
for protocol in &self.code {
let mut new_rules = initial_rules.to_vec();
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-15 12:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 12:10 [pve-devel] [PATCH docs/firewall/manager/network/proxmox{-ve-rs, -firewall} v4 00/18] add forward chain firewalling for hosts and vnets Stefan Hanreich
2024-11-15 12:10 ` [pve-devel] [PATCH proxmox-ve-rs v4 01/18] firewall: add forward direction Stefan Hanreich
2024-11-15 12:10 ` [pve-devel] [PATCH proxmox-ve-rs v4 02/18] firewall: add bridge firewall config parser Stefan Hanreich
2024-11-15 12:10 ` [pve-devel] [PATCH proxmox-ve-rs v4 03/18] config: firewall: add tests for interface and directions Stefan Hanreich
2024-11-15 12:10 ` [pve-devel] [PATCH proxmox-ve-rs v4 04/18] host: add struct representing bridge names Stefan Hanreich
2024-11-15 12:10 ` [pve-devel] [PATCH proxmox-firewall v4 05/18] nftables: derive additional traits for nftables types Stefan Hanreich
2024-11-15 12:10 ` [pve-devel] [PATCH proxmox-firewall v4 06/18] sdn: add support for loading vnet-level firewall config Stefan Hanreich
2024-11-15 12:10 ` [pve-devel] [PATCH proxmox-firewall v4 07/18] sdn: create forward firewall rules Stefan Hanreich
2024-11-15 12:10 ` Stefan Hanreich [this message]
2024-11-15 12:11 ` [pve-devel] [PATCH pve-firewall v4 09/18] sdn: add vnet firewall configuration Stefan Hanreich
2024-11-15 12:11 ` [pve-devel] [PATCH pve-firewall v4 10/18] api: add vnet endpoints Stefan Hanreich
2024-11-15 12:11 ` [pve-devel] [PATCH pve-firewall v4 11/18] firewall: move to arrow syntax for calling functions Stefan Hanreich
2024-11-15 12:11 ` [pve-devel] [PATCH pve-manager v4 12/18] firewall: add forward direction to rule panel Stefan Hanreich
2024-11-15 12:11 ` [pve-devel] [PATCH pve-manager v4 13/18] firewall: add vnet to firewall options component Stefan Hanreich
2024-11-15 12:11 ` [pve-devel] [PATCH pve-manager v4 14/18] firewall: make base_url dynamically configurable in " Stefan Hanreich
2024-11-15 12:11 ` [pve-devel] [PATCH pve-manager v4 15/18] sdn: add firewall panel Stefan Hanreich
2024-11-15 12:11 ` [pve-devel] [PATCH pve-manager v4 16/18] firewall: rules: show warning when creating forward rules Stefan Hanreich
2024-11-15 12:11 ` [pve-devel] [PATCH pve-network v4 17/18] firewall: add endpoints for vnet-level firewall Stefan Hanreich
2024-11-15 12:11 ` [pve-devel] [PATCH pve-docs v4 18/18] firewall: add documentation for forward direction and vnet zone Stefan Hanreich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241115121109.170200-9-s.hanreich@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=w.bumiller@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox