Paul Schoenfelder

I believe this can be closed @bobbinth - we have all of the necessary primitives for source-level debug info, with only a couple of minor questions outstanding, off the top...

Something to note here: this could be done safely using some of my suggestions on the topic of a "Miden component model". Specifically, the ability to switch between arbitrary contexts,...

I think it would be great to add support for it! I'm thinking I'd like to approach adding the ability to plug in these kinds of extensions, and implement the...

@rockerBOO I've pushed a branch `feature/extensions`. Take a look at `lib/extensions/*` where I've defined a behaviour for extensions, with an example extension for handling `CAP LS` responses. In `client.ex` you'll...

Good point on the extension naming! I'm pretty unfamiliar with the IRCv3 stuff as well at the moment, but that link you provided has some decent documentation, it'll just take...

I think we just need to expand [this function](https://github.com/bitwalker/exirc/blob/master/lib/exirc/client.ex#L676) to send a new event (maybe :custom or :unrecognized) or something, that way your handler can accept all unrecognized messages and...

I wouldn't mind that, something to keep in mind though is that something received by that callback may not actually be a command (it could just be garbage), so we...

This is the same class of issue as SQL injection, in that unknown (theoretically attacker-controlled) content is being directly passed through to an API that expects text that may contain...

Yes, I'm aware, I'm saying that it is perfectly valid to call `msg/4` with content containing newlines, it gets converted into multiple messages as per the protocol.

Those are all great suggestions! Here are my thoughts: - Latency, timeouts, and dropped messages can all be handled by implementing an alternative distribution carrier I think, and running all...