Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build-std #274

Open
4 tasks
nikomatsakis opened this issue Feb 18, 2025 · 3 comments
Open
4 tasks

build-std #274

nikomatsakis opened this issue Feb 18, 2025 · 3 comments
Assignees
Milestone

Comments

@nikomatsakis
Copy link
Contributor

Metadata
Point of contact @davidtwco
Team(s) cargo
Goal document 2025h1/build-std

Summary

Write an RFC for a minimum viable product (MVP) of build-std which has the potential to be
stabilised once implemented (as opposed to the currently implemented MVP which is only suitable for
experimentation and testing), and then implement it.

Tasks and status

@nikomatsakis
Copy link
Contributor Author

This issue is intended for status updates only.

For general questions or comments, please contact the owner(s) directly.

@davidtwco
Copy link
Member

An initial update on what we've been up to and some background:

  • This goal is submitted on behalf of the Rust team at Arm, but primarily worked on by @adamgemmell. Anyone interested can always contact me for updates and I'll keep this issue up-to-date.
  • Our team has been trying to make progress on build-std by completing the issues in rust-lang/wg-cargo-std-aware but found this wasn't especially effective as there wasn't a clearly defined scope or desired outcome for most issues and the relevant teams were lacking in the necessary context to evaluate any proposals.
  • We've since had discussions with the Cargo team and agreed to draft a document describing the use cases, motivations and prior art for build-std such that the Cargo team can feel confident in reviewing any further proposals.
    • @adamgemmell shared an initial draft of this in #t-cargo on Zulip and it is undergoing further revisions following feedback.
    • Following reaching a shared understanding of the context of the feature, @adamgemmell will then draft a complete proposal for build-std that could feasibly be stabilised. It will describe the use cases which are and are not considered in-scope for build-std, and which will feature in an initial implementation.
  • @davidtwco is ensuring that whatever mechanism that is eventually proposed to enable build-std to work on stable toolchains will also be suitable for the Rust for Linux project to use when building core themselves.

@davidtwco
Copy link
Member

A small update, @adamgemmell shared revisions to the aforementioned document, further feedback to which is being addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants