You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tried to build the examples and with the only dep being nx I got the follow issue:
Compiling linked_list_allocator v0.10.5
Buildingerror[E0599]: no method named `dangling` found for struct `Layout` in the current scope
--> C:\Users\lucy\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\linked_list_allocator-0.10.5\src\lib.rs:273:60
|
273 | return Ok(NonNull::slice_from_raw_parts(layout.dangling(), 0));
| ^^^^^^^^
|
help: there is a method `dangling_ptr` with a similar name
|
273 | return Ok(NonNull::slice_from_raw_parts(layout.dangling_ptr(), 0));
| ++++
For more information about this error, try `rustc --explain E0599`.
Building
error: could not compile `linked_list_allocator` (lib) due to 1 previous error
@XorTroll@pantsman0 I am very interested in contributing to the aarch64-switch-rs org,
I could for example compare allocator crates, then make a PR, depending on what you think.
Do you have some sort of direct channel or should we continue communication in this thread?
Activity
XorTroll commentedon Mar 21, 2026
Have you tried updating nightly Rust? I believe that fixed the issue on my end
sermuns commentedon Mar 21, 2026
danglingwas renamed todangling_ptr: rust-lang/rust#148769 (comment)sermuns commentedon Mar 21, 2026
One shitty workaround is to pin to the nightly version before this was merged, e.g. creating
rust-toolchain.tomlwithBut if I understand correctly, the real solution is for
linked_list_allocatorto change their code?sermuns commentedon Mar 21, 2026
I have opened PR on
linked_list_allocator: rust-osdev/linked-list-allocator#90pantsman0 commentedon Mar 31, 2026
@XorTroll There doesn't seem to be much urgency on the LL allocator side - we could consider a similar allocator such as
buddy_system_allocator?XorTroll commentedon Apr 2, 2026
Yeah absolutely, I'd rather rely on a somewhat maintained allocator to avoid these dependency issues in the future
sermuns commentedon Apr 2, 2026
@XorTroll @pantsman0 I am very interested in contributing to the
aarch64-switch-rsorg,I could for example compare allocator crates, then make a PR, depending on what you think.
Do you have some sort of direct channel or should we continue communication in this thread?
pantsman0 commentedon Apr 2, 2026
aarch64-switch-rs/nx#60 @sermuns
Feel free to put some options in there and we can make a decision from there