Fix compilation errors with latest Rust nightly #28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes issue #19 by resolving compilation errors that occur when using the latest Rust nightly compiler. The errors were caused by unstable features that have been deprecated, removed, or changed in recent Rust versions.
Changes Made
const_deref
,const_result_drop
,default_free_fn
,generators
, etc.)impl_trait_in_assoc_type
for opaque types and updatedgenerators
tocoroutines
~const
trait bounds that are no longer supported in the current Rust nightlyimpl Trait
in associated types to concretestd::vec::IntoIter<T>
types to avoid compiler constraintsstd::default::default
function calls withDefault::default()
data-rs
andmem-rs
dependenciesTesting
The project now compiles successfully with Rust nightly 1.91.0-nightly (565a9ca63 2025-09-10) with only warnings related to unused imports and dead code, but no compilation errors.
Verification
Before the fix:
After the fix:
$ cargo +nightly check # Compiles successfully with only warnings
Test plan
impl Trait
in associated types is unstable (on latest rust nightly and git dependency) #19 are resolved🤖 Generated with Claude Code
Resolves #19