Brendan A R Sechter

Does `crank build --release --example=hello_world --device` work locally for you with Playdate SDK 1.13.1?

It works on my newer MacBook, but fails on the older iMac. MacBook details below. Not sure what the problem is, but it is not SDK 1.13.1. ```bash $ ex...

No contest. Without doing any deep digging, ::try_into appears to be implicitly called, but the function is not making it into the binary. Reverting to older versions of Rust on...

> I am starting to think it is a Rust bug in that most recent nightly. A couple of questions. 1. Does crankstart still need to rely on nightly? Is...

FWIW, someone I asked thought that it might have to do with the `-Z build-std` flags. So far as I can tell, these flags are passed in by **crank**, and...

> I use stable 1.67.1 with crank/crankstart If stable works, using stable instead of nightly strikes me as the best solution. (On the macOS 11.7.4 x86_64, stable 1.68.0 (2c8cc3432 2023-03-06)...

New version of **crank** confirmed to be working on my machine. When using stable, compiling for hardware worked, but compiling for the simulator failed. Using an earlier version of rust...

```bash $ rustup default stable $ cargo clean $ crank build --release --device *snip* Finished release [optimized] target(s) in 19.82s $ crank build --release *snip* error[E0554]: `#![feature]` may not be...

[dtolnay/thiserror#64](https://github.com/dtolnay/thiserror/pull/64) has been closed. Before the PR was closed, [`snafu`](https://crates.io/crates/snafu) was mentioned as a `no_std` alternative. There is also a [`thiserror-core`](https://crates.io/crates/thiserror-core) crate.

I can think of three sensible approaches for handling a dynamic time delta. 1. A breaking change that moves `dt` to the `Ahrs` trait interface seems like the most graceful...