all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: 54509@debbugs.gnu.org, mekeor@posteo.de, maximedevos@telenet.be
Subject: [bug#54509] bump: make rust-cargo understand rust-edition2021 which rustc already does
Date: Sat, 02 Jul 2022 11:27:09 +0000	[thread overview]
Message-ID: <2CEC1F61-FC4D-4E59-BFCF-6698380038A6@tobias.gr> (raw)
In-Reply-To: <87sfnk4e3j.fsf@posteo.de>

Hi, 

λ cargo new foo
     Created binary (application) `foo` package
λ cd foo
λ cargo run
λ sed -i 's/2018/2021/' Cargo.toml
λ cargo run
   Compiling foo v0.1.0 (/home/nckx/c/foo)
    Finished dev [unoptimized + debuginfo] target(s) in 1.11s
     Running `target/debug/foo`
Hello, world!
λ echo 'axum = "0.5.4"' >> Cargo.toml
λ cargo run
[...]
Downloaded httpdate v1.0.2
   Compiling foo v0.1.0 (/home/nckx/c/foo)
    Finished dev [unoptimized + debuginfo] target(s) in 54.46s
     Running `target/debug/foo`
Hello, world!

Did you read the entirety of Maxime's reply?  How are you controlling your environment?

Kind regards,

T G-R

Sent on the go.  Excuse or enjoy my brevity.




  reply	other threads:[~2022-07-02 11:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 17:46 [bug#54509] rust-cargo: Update to 0.60.0 to support Edition2021 projects Paul Alesius
2022-03-21 18:46 ` Maxime Devos
2022-03-21 20:59   ` Paul Alesius
2023-02-09 13:18     ` bug#54509: " Maxim Cournoyer
2022-06-29 22:57 ` [bug#54509] bump: make rust-cargo understand rust-edition2021 which rustc already does Mekeor Melire
2022-06-30  8:10   ` Maxime Devos
2022-07-01 21:48     ` Mekeor Melire
2022-07-02 11:27       ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-07-02 11:35         ` Tobias Geerinckx-Rice via Guix-patches via
2022-07-06 14:06           ` Mekeor Melire

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=2CEC1F61-FC4D-4E59-BFCF-6698380038A6@tobias.gr \
    --to=guix-patches@gnu.org \
    --cc=54509@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=me@tobias.gr \
    --cc=mekeor@posteo.de \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.