Gen_statem: looping with {next_event, internal, _} blocks calls

[rlipscombe]

@NelsonVides

I’d say it depends on what the simulated work is really doing here

The actual work is something that takes 500ms, which is why I felt comfortable simulating it with a sleep

@NelsonVides

it could be outsourced to a separate process that will tell the main one when it’s done its work

And, in fact, it’s a synchronous call to another process. If I replace it with send_request…check_response, everything’s fine. It’s just harder to read the code – I quite liked the simplicity of the synchronous thing.