ryan

We fixed a couple of things on the polyfils in `0.2.4`, (#220) which is probably what brought this to light.

hey thanks for the issue, where is the `Hertz` type from? i might not have the full picture but, it seems like that'd be a missing conversion in `embedded-time` (or...

i am _not at all_ sure this is it but, usually with ARM we specify the GNU/gcc linker rather than LLD with `.cargo/config`: ``` [target.armv7-unknown-linux-gnueabihf] linker = "arm-linux-gnueabihf-gcc" ``` have...

ahh `can't link soft-float modules with double-float modules` is familiar, though i can't find the issues i tracked down to solve this. on armhf this is sometimes resolved by adding...

> Who is "we" and why are you doing that? org project, because inexplicably when you start linking external c libraries the linker seems to break in a variety of...

iiinteresting, i'd echo @eldriun's thoughts, this seems neat but also like a bit of a compatibility problem / not something _most_ users should need to care about... would it be...

huh, interesting failure! i have a bit of async experience but, the internals of this are unfamiliar to me... @mgottschlag no obligations but, any ideas? absolutely grasping at straws but:...

it's super cursed but i think it'd be useful to document the implications of unwinding across ffi boundaries for c/rust interop and supporting the piecewise approach to moving to rust....

@tustvold excellent writeup, thanks for exploring this! i've been writing a bunch of non-embedded futures code recently and, as interesting as the concept is, i don't think they're a good...

> You talked about "naturally async" and "native async". As someone who's been following the async story from afar, what would that involve? async/await? Generators? Something else? by "naturally async"...