Hi Pedro. To clarify the original email. The proposal is not to create a new repository to start Rust std work. Rather, it is to move all the per-existing work that I have done for implementing std since the beginning of GSoC. This work can be found in my personal fork [1]. A significant portion of std is already in a working state for DXE UEFI and is at a point that a PR can be opened in a few weeks upstream to get it merged. A fork under Tianocore would allow more people, form both Rust and Tianocore side to experiment/improve the std, with the final goal of getting it all merged in upstream Rust. Yours Sincerely Ayush Singh [1]: https://github.com/Ayush1325/rust/tree/uefi-std-rebase On 8/1/22 22:56, Pedro Falcato wrote: > 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, 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 > > > > > >