no_std for wtf8, sre_engine, compiler-core, literal#7051
Conversation
📝 WalkthroughWalkthroughMultiple crates migrate to no_std compilation by adding Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~22 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Sorry, something went wrong.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@crates/wtf8/src/lib.rs`:
- Around line 36-46: The workspace dependency for itertools must be configured
for no_std; update the Cargo.toml entry for itertools to disable default
features and enable its alloc support by setting itertools = { version =
"0.14.0", default-features = false, features = ["use_alloc"] } so the crate
using #![no_std] and alloc (see extern crate alloc and uses like
itertools::Either / itertools::Itertools) compiles without pulling in std.
Sorry, something went wrong.
cf83008
into
RustPython:main
Feb 8, 2026
Summary by CodeRabbit
New Features
Refactor