From: tjkirch <tjkirch@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rust-analyzer: update to 2022.01.03.
Date: Mon, 17 Jan 2022 20:42:28 +0100 [thread overview]
Message-ID: <20220117194228.glbZGKv3TfmrGZrz3lGAIARQfwD1vqgXAW0K88MIIFI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34856@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
New comment by tjkirch on void-packages repository
https://github.com/void-linux/void-packages/pull/34856#issuecomment-1014841625
Comment:
For the record, I tried updating this PR to rust-analyzer 2022-01-17, but it fails to build because we don't have Rust 1.58 yet. As of [two days ago](https://github.com/rust-analyzer/rust-analyzer/commit/91279db2b4dff5cc77a9f34a2212e93490676c46#diff-fe57070ff64dbee9c061031533b3b75f6ef360f3a794aefad62f6849be2caaa3R16) it relies on [captured identifiers in format strings](https://blog.rust-lang.org/2022/01/13/Rust-1.58.0.html#captured-identifiers-in-format-strings). We could probably update to 2022-01-10, but hopefully we have Rust 1.58 soon.
next prev parent reply other threads:[~2022-01-17 19:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 22:31 [PR PATCH] " tjkirch
2022-01-05 18:40 ` tjkirch
2022-01-05 19:03 ` ericonr
2022-01-05 19:22 ` tjkirch
2022-01-05 19:23 ` ericonr
2022-01-05 19:23 ` ericonr
2022-01-17 19:42 ` tjkirch [this message]
2022-01-17 23:56 ` ericonr
2022-01-18 0:04 ` tjkirch
2022-02-27 12:13 ` tranzystorek-io
2022-02-27 19:01 ` tjkirch
2022-04-05 2:32 ` Goorzhel
2022-06-15 21:18 ` classabbyamp
2022-06-15 21:18 ` [PR PATCH] [Closed]: " classabbyamp
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=20220117194228.glbZGKv3TfmrGZrz3lGAIARQfwD1vqgXAW0K88MIIFI@z \
--to=tjkirch@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).