Arnout Engelen

I think this probably relies on the markdown library we're using - #81 might be relevant

We don't close issues that are of the "not urgent but might be nice some day" category, so yes, they can stick around for a long time ;). Your help...

Thanks for the quick reply. That is actually an interesting proposal - though extending it to the other 3 arrow types (`A\\>B`, `A\>>B`, `A\\>>B`) seems a bit nasty. An alternative...

Ah, looks like the attributes are added at the end of the line in #74. So representing https://w3.cs.jmu.edu/bernstdh/Web/CS460/study-aids/exam2-sample.php as: ``` default-drop = 1 (...) T->R: F3 R->T: ACK 4 [drop...

Thanks for the ping, that looks quite cool! Indeed a bit 'goto-ish' but that is probably hard to avoid - my `drop=x` proposal above is not much better in that...

``` A->B: Trigger broadcast B->A: Broadcast message =B->C: Broadcast message =Note right of C: Yay B->A: Ack broadcast ``` 

You mean this diagram is ambiguous because it could also be interpreted to mean A and C sent 'broadcast' messages to each other? I suppose that makes sense - but...

Ah yes, that's a more realistic example of the same ambiguity indeed :).

@notxcain hmm, can you give an example of a situation where it would be acceptable for `applyEvent` to throw (c.q. return an error)? Typically you'd want to do any validation...

I wholeheartedly agree we want akka-typed to be typed and total! With persistence, the state is updated after deciding to persist the event - because on recovery (for example after...