From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Max Carrara <m.carrara@proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 pve-common 00/12] Introduce and Package PVE::Path & PVE::Filesystem
Date: Thu, 2 Jan 2025 14:53:18 +0100 [thread overview]
Message-ID: <47ba1e8e-c5d1-4873-91c4-9927b3b72e8c@proxmox.com> (raw)
In-Reply-To: <9e522634-51ff-493a-bcdb-aba560d17d6a@proxmox.com>
Am 02.01.25 um 14:46 schrieb Fiona Ebner:
> Am 20.12.24 um 19:51 schrieb Max Carrara:
>> Introduce and Package PVE::Path & PVE::Filesystem - v2
>> ======================================================
>
> Just an idea, but I'd like to have a discussion about it: Instead of
> using Perl for such new general helper modules, would it be nicer to use
> Rust+perlmod?
>
> If our long-term goal is to migrate the Proxmox VE Perl code to Rust,
> then we need to switch these modules over at some point in any case (or
> drop them after switching over all users of the modules). Are there good
> reasons not to start out with Rust+perlmod already?
>
> You state that you (also) took inspiration from Rust's `std::path` so
> could we just use that itself, wrapping via perlmod? Or would the
> wrapping be too ugly here or lead to performance issues?
Or depending on whether it's nicer, also wrapping helpers from
proxmox-sys and friends where we already have similar functionality in
our Rust code.
_______________________________________________
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:[~2025-01-02 13:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 18:51 Max Carrara
2024-12-20 18:51 ` [pve-devel] [PATCH v2 pve-common 01/12] introduce PVE::Path Max Carrara
2025-01-08 14:05 ` Wolfgang Bumiller
2025-01-09 9:56 ` Max Carrara
2025-01-09 11:06 ` Wolfgang Bumiller
2025-01-09 12:56 ` Max Carrara
2024-12-20 18:51 ` [pve-devel] [PATCH v2 pve-common 02/12] test: add directory for tests of PVE::Path module Max Carrara
2024-12-20 18:51 ` [pve-devel] [PATCH v2 pve-common 03/12] test: add tests for path_is_absolute and path_is_relative of PVE::Path Max Carrara
2024-12-20 18:51 ` [pve-devel] [PATCH v2 pve-common 04/12] test: add tests for path_components " Max Carrara
2024-12-20 18:52 ` [pve-devel] [PATCH v2 pve-common 05/12] test: add tests for path_join " Max Carrara
2024-12-20 18:52 ` [pve-devel] [PATCH v2 pve-common 06/12] test: add tests for path_push " Max Carrara
2024-12-20 18:52 ` [pve-devel] [PATCH v2 pve-common 07/12] test: add tests for path_parent " Max Carrara
2024-12-20 18:52 ` [pve-devel] [PATCH v2 pve-common 08/12] test: add tests for path_starts_with, path_ends_with, path_equals Max Carrara
2024-12-20 18:52 ` [pve-devel] [PATCH v2 pve-common 09/12] test: add tests for file path ops functions of PVE::Path Max Carrara
2024-12-20 18:52 ` [pve-devel] [PATCH v2 pve-common 10/12] test: add tests for path_normalize " Max Carrara
2024-12-20 18:52 ` [pve-devel] [PATCH v2 pve-common 11/12] introduce PVE::Filesystem Max Carrara
2024-12-20 18:52 ` [pve-devel] [PATCH v2 pve-common 12/12] debian: introduce package libproxmox-fs-path-utils-perl Max Carrara
2025-01-02 13:46 ` [pve-devel] [PATCH v2 pve-common 00/12] Introduce and Package PVE::Path & PVE::Filesystem Fiona Ebner
2025-01-02 13:53 ` Fiona Ebner [this message]
2025-01-02 15:54 ` Max Carrara
2025-01-03 9:49 ` Fiona Ebner
2025-01-03 10:41 ` Thomas Lamprecht
2025-01-03 12:37 ` Fiona Ebner
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=47ba1e8e-c5d1-4873-91c4-9927b3b72e8c@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=m.carrara@proxmox.com \
--cc=pve-devel@lists.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