Skip to content

Conversation

alexcrichton
Copy link
Member

To make progress on #18585 we're paring down the distribution to theoretically
"only libstd", and this commit makes progress on this by removing the rlibc
crate from the distribution.

The crate has now been moved into an external cargo package located in the rust
lang organization 1

cc #18585

To make progress on rust-lang#18585 we're paring down the distribution to theoretically
"only libstd", and this commit makes progress on this by removing the rlibc
crate from the distribution.

The crate has now been moved into an external cargo package located in the rust
lang organization [1]. This is a breaking change due to this removal, and
existing crates depending on `rlibc` should use the Cargo crate instead.

[1]: https://github.com/rust-lang/rlibc

[breaking-change]
cc rust-lang#18585
alexcrichton added a commit to alexcrichton/rust that referenced this pull request Nov 6, 2014
@bors bors merged commit b39f1dc into rust-lang:master Nov 7, 2014
@alexcrichton alexcrichton deleted the no-more-rlibc branch November 7, 2014 02:12
lnicola pushed a commit to lnicola/rust that referenced this pull request Dec 11, 2024
fix: Fix parser getting stuck for bad asm expressions
lnicola pushed a commit to lnicola/rust that referenced this pull request Jul 18, 2025
Even when at curly braces, otherwise the parser can get stuck.

This has happened in the past in rust-lang#18625, but it was just worked around instead of handling the root of the problem. Now this happened again in rust-lang#20171. IMO we can't let `err_and_bump()` not bump, that's too confusing and invites errors. We can (as I did) workaround the worse recovery instead.
ZuseZ4 pushed a commit to ZuseZ4/rust that referenced this pull request Jul 18, 2025
Even when at curly braces, otherwise the parser can get stuck.

This has happened in the past in rust-lang#18625, but it was just worked around instead of handling the root of the problem. Now this happened again in rust-lang#20171. IMO we can't let `err_and_bump()` not bump, that's too confusing and invites errors. We can (as I did) workaround the worse recovery instead.
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.

2 participants