public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
	Ayush Singh <ayushdevel1325@gmail.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	 Michael Kubacki <mikuback@linux.microsoft.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>,
	 "Gaibusab, Jabeena B" <jabeena.b.gaibusab@intel.com>
Subject: Re: [edk2-devel] Proposal to move Rust std work to a Repository under Tianocore
Date: Mon, 1 Aug 2022 18:26:31 +0100	[thread overview]
Message-ID: <CAKbZUD0UjWN3TFx0hsNT9YH10R7DeTxk16DqeGT2v2aOSdeBgQ@mail.gmail.com> (raw)
In-Reply-To: <33ac1f75-d6c9-2093-8701-698a3e553d64@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]

Hi,

May I suggest you just port the bare rust language (no crates, no std) to
EDK2? It seems far more plausible to expect people to use a cut down
version with some bindings to the rest of the project instead of hoping
people just use the whole of rust, a lot of which isnt proven (or even used
AFAIK) in bare metal projects. Porting just the bare minimum is way more
realistic in my opinion.

Thanks,
Pedro

On Mon, 1 Aug 2022, 18:02 Ayush Singh, <ayushdevel1325@gmail.com> wrote:

> Hello everyone. In the previous email thread [1], I discussed the
> proposal to move Rust std work to edk2-staging and mentioned its
> potential problems. After some discussion with mentors, we arrived at
> the conclusion to have a rustlang [2] fork under the Tianocore
> organization, and move all the std related work there. We can then open
> a PR upstream from there, while allowing PRs in this repository. This
> should help provide an easier and streamlined way for people to
> experiment and work on this project while it is in the process of being
> merged upstream.
>
>
> For a status update about tests:
>
> - passed: 12797
>
> - failed: 40
>
> - ignored: 375
>
>
> Yours Sincerely,
>
> Ayush Singh
>
>
> [1]: https://edk2.groups.io/g/devel/message/91989
>
> [2]: https://github.com/rust-lang/rust
>
>
>
> 
>
>
>

[-- Attachment #2: Type: text/html, Size: 2007 bytes --]

  reply	other threads:[~2022-08-01 17:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 17:02 Proposal to move Rust std work to a Repository under Tianocore Ayush Singh
2022-08-01 17:26 ` Pedro Falcato [this message]
2022-08-01 17:39   ` [edk2-devel] " Ayush Singh
2022-08-01 19:06     ` Pedro Falcato
2022-08-01 19:14       ` Michael D Kinney
2022-08-01 19:36       ` Ayush Singh
2022-08-01 17:50   ` Ayush Singh
2022-08-01 18:07     ` Yao, Jiewen
2022-08-01 18:55       ` Ayush Singh
2022-08-01 21:16         ` Leonardo Garcia
2022-08-01 18:13 ` Michael D Kinney
2022-08-01 19:01   ` Ayush Singh
2022-08-01 19:08     ` Michael D Kinney

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-list 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=CAKbZUD0UjWN3TFx0hsNT9YH10R7DeTxk16DqeGT2v2aOSdeBgQ@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /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