From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 7A590158008 for ; Fri, 16 Jun 2023 14:48:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 99E1CE092B; Fri, 16 Jun 2023 14:48:28 +0000 (UTC) Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 60674E08F5 for ; Fri, 16 Jun 2023 14:48:28 +0000 (UTC) Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-9741caaf9d4so110763966b.0 for ; Fri, 16 Jun 2023 07:48:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686926906; x=1689518906; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=DBMFtrNwL05GB6YpT7rB2aWeGiriKa2fSvzk4me6u+4=; b=neWX0cE0D4Cr/OEsnU6PaB1HQdYGuewNHKwhi6x53l30123pQTuar8hvNuZnAK+gh/ bKmfZ/43dfJIwrfVt+kRanG5nIE2rzz4zH7b03q4y5FW01AaQEELFHxbgeSbVqTe8Jn5 kLebKOwyrT2DLnMj8o8YHNshRlh/IyikFBXbbS7iPh1d3TcxMClCdZ0ts8PUbCCyF30d e8ok6pwxfAXzdIEfgCY2YHRZGM8a/7aJ8B06dQ7NoUmObv2D8kGC/XMu8+c+q7ZBgAMX iPI7Q0/qIGgujeulyUgCLss6s74ot8+jxTUPNAZb5SmkmdOTi6LKtfAJqMJFx5CYx+Ei k1iQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686926906; x=1689518906; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=DBMFtrNwL05GB6YpT7rB2aWeGiriKa2fSvzk4me6u+4=; b=AVK7Jyhnm7L2KYY7TURtQeh7CRdHb8AqLEjgJ8kV0GbwKJNo0i5UfJvLX7uPAIJ/r9 VxbSxg4xDo5L6NcFTaFTiiqeqcu89ehKIr0JicWyOJp1g77g7K7weLzGxkalq6cO8gV0 wNxo1H0OMrgZtdtdC2xjATgZRCVt88MjlXpHH1KPJFyJeBfc6KQ3qs7mA6doT4EDTPZq p8wbEXYYcs2ZBITbVi/amFcoLkGJ0ZzhwvElcbYiNtJFU48mKGnBRKz73KYq2jNjU4zQ v2Tp1UWXyg63Zf6sVTucrwI4zofPeezyE3aeFqFYuEzBkV3JeHSOg+dzFRHsmLn34Lgn J02A== X-Gm-Message-State: AC+VfDzEJOgRajnGzS8IxTzdY4DxMWUnZ/VFQInYCAyo4sm49UggnBXT jVgjCGrJhEILpaUXspUFtWnznws/dxMahmwNrVtib+rdhupgjQ== X-Google-Smtp-Source: ACHHUZ7XMCypt32icqdVswMnqrsgKIwvPSXXA5FaKjO4Ca3sGupwNLsOUELsCfIjaD9MWwrzfAi3KR35kAamNLxghuk= X-Received: by 2002:a17:906:5d0c:b0:982:26c5:d05c with SMTP id g12-20020a1709065d0c00b0098226c5d05cmr2504491ejt.7.1686926906181; Fri, 16 Jun 2023 07:48:26 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <20230616120739.8656-1-mgorny@gentoo.org> <20230616120739.8656-5-mgorny@gentoo.org> In-Reply-To: <20230616120739.8656-5-mgorny@gentoo.org> From: Denis Lisov Date: Fri, 16 Jun 2023 17:48:14 +0300 Message-ID: Subject: Re: [gentoo-dev] [PATCH 4/5] cargo.eclass: Support separating crate names/versions via slash To: gentoo-dev@lists.gentoo.org Cc: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 1092f17b-10d3-4bfc-8b80-9c3e9d579be9 X-Archives-Hash: 6c58813fc87926f76136089a0d5d16c8 Hello Micha=C5=82, On Fri, Jun 16, 2023 at 3:09=E2=80=AFPM Micha=C5=82 G=C3=B3rny wrote: > Support specifying crate names and versions separated by forward slashes > rather than hyphens. Since slashes are not valid in crate names, this > makes splitting the tokens trivial and free of regular expressions. > Effectively, the slash variant is roughly 180% faster: As a developer using Rust I want to note that Cargo has a concept of "package ID specification"[1] that usually uses pkgname@version syntax, but AFAIK there's no prior art for using pkgname/version in the ecosystem. Could it make sense to use pkgname@version for consistency? Regards, Denis Lisov. [1]: https://doc.rust-lang.org/cargo/reference/pkgid-spec.html