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

Support no_std in Prost toolchain #3180

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

fionera
Copy link
Contributor

@fionera fionera commented Jan 10, 2025

No description provided.

@fionera fionera force-pushed the prost-no-std branch 4 times, most recently from dfc73de to 4062960 Compare January 10, 2025 21:13
Copy link
Collaborator

@UebelAndre UebelAndre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Just one minor request!

Copy link
Collaborator

@UebelAndre UebelAndre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One last nit and I think you can delete rust_prost.md since docs are now generated directly from the bzl source file. Devs no longer need to render them and add them to their PRs 😄

Copy link
Collaborator

@UebelAndre UebelAndre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@UebelAndre UebelAndre added this pull request to the merge queue Jan 28, 2025
@UebelAndre UebelAndre removed this pull request from the merge queue due to a manual request Jan 28, 2025
Copy link
Collaborator

@UebelAndre UebelAndre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, is there some sort of integration test you can add that uses this new flag?

@fionera
Copy link
Contributor Author

fionera commented Feb 11, 2025

If you give me an example, I could take a look

@UebelAndre
Copy link
Collaborator

If you give me an example, I could take a look

Like any of the cases here: https://github.com/bazelbuild/rules_rust/tree/5226882efee4c3f1f2b68940b06fad9ad070f8b1/extensions/prost/private/tests

if there’s a single test that that uses use_no_std then there is some regression testing to know if a future change breaks this feature.

@UebelAndre
Copy link
Collaborator

Like any of the cases here: https://github.com/bazelbuild/rules_rust/tree/5226882efee4c3f1f2b68940b06fad9ad070f8b1/extensions/prost/private/tests

if there’s a single test that that uses use_no_std then there is some regression testing to know if a future change breaks this feature.

Let me know if you still have questions! Happy to get this merged but it'll be super helpful down the line to have at least 1 regression test.

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

Successfully merging this pull request may close these issues.

3 participants