sigurd4

@MarcelRobitaille No. A temporary (non-ideal) solution is to lint and write the code in VSCode, and flash the device with Arduino IDE. If you use the newest version of Arduino...

@maxgerhardt I no longer have access to the Portenta H7 in question, because the project i was on is now over. Good luck

No, I did not find a workaround

Never mind. I got rid of the type alias, and avoided doing specialization in `private::_Copied`, yet i get the same error on docs.rs. The original hypothesis i had for why...

Managed to make it build on docs.rs by excluding feature `opt_cell`. So clearly the problem is located somewhere in `opt_cell.rs`. For now i'll just exclude the feature in the documentation

Thanks. That's a very useful tool. I ran `cargo docs-rs` and got the same error. Does not happen if i run `cargo build` normally. If i omit feature `opt_cell` from...

So it's clearly not a resource limit issue, it's probably due to using experimental rust language features like specialization i think. I suspect it might fail on the specialization i...

Weird... I tried just commenting out everything in the `opt_cell.rs` file except the following and i still got the same error, even after doing `cargo clean`. ```rust pub struct OptCell(T);...

If i make a similar struct in another clean project, no error occurs, so it has to be something about my repo specifically. Very strange. It happens only when the...

Rust ICE when doing cargo docs-rs: ``` thread 'rustc' panicked at /rustc/426d1734238e3c5f52e935ba4f617f3a9f43b59d/compiler/rustc_type_ir/src/predicate.rs:532:17: Cannot turn `UnevaluatedConst` into `AliasTy` stack backtrace: 0: 0x7db52efcd1a5 - std::backtrace::Backtrace::create::h2021bf191a8739ac 1: 0x7db52d4a4555 - std::backtrace::Backtrace::force_capture::h1c4a4f7d7b3cc85e 2: 0x7db52c6306fe -...