Maxim Deloof

So I've been thinking about this for a while, and although I initially thought I'd be able to statically allocate the space for the futures, I currently don't see how...

I found some time to work on this today. I've been able to resolve the bug and now have something that seems to work (code is on [`no_std_async`](https://github.com/mdeloof/statig/tree/no_std_async)). I plan...

I definitely want to add some way to visualise the state machines, though I'm still thinking about the best way to go about it. The tree representation is a nice...

Yes, like you said, you would have to place some restrictions on the logic in the event handlers to make sure this approach is able to correctly cover the entire...

Hi Dylan Would reborrowing `value` be an option for you? ```rust mod example_reborrow { struct Foo; struct Event, } type Ctx) { unimplemented!() } fn example(mut event: Event

Hi, thanks for trying out `statig`! Having some sort of visualisation of state machines has been on my todo list for some time now. The major issue I don't really...

Resolved by #49

In the meantime I've seen that the AT log port contains an unhandled exception `Guru Meditation Error: Core 0 panic'ed (LoadProhibited)` which causes a reboot, so that probably explains the...

Hi, I have enabled the AT logs and rerun the tests, and it appears that the extra logs significantly lower the data rate. So far we have not seen the...

@christianheussy It's looking good! I'm wondering if we should maybe opt to simply use `custom` (or maybe `manual` ) instead of `custom_state` as it's already a sub-attribute of `state`?