Oxidise

[rerpha]

Convert saluki to rust.

Changes to note:

• listen and consume have been merged, as they were quite similar anyway. README and --help should clarify how to use consume (which is aliased to listen for muscle memory's sake!)
• play has not been carried over as I ran out of time to be able to call this personal development. rewrite play in rust #50 exists to add it when we need to use it again.
• howl is a bit faster than python, though I haven't tried the "cheat" way of only constructing one set of det values but sending them x times a frame.
• have added a dockerfile so you don't actually need rust installed to use saluki.
• I haven't gone mad with unit tests as again I've run out of time (I know I know TDD and so on...)

also note that the CI is currently failing at the time of writing but only because one of the apt mirrors seems to be 404ing? working now

I may also need a hand benchmarking howl plz @Tom-Willemsen

[Tom-Willemsen]

I'll give this a more thorough functional test tomorrow...

[Tom-Willemsen]

I know this is pretty much exactly how I'd written it in the python too, with a zillion arguments, but I think the more extensible approach is to pull all of the "howl config" arguments into a HowlConfig struct, instantiated once in main, and passed through as &HowlConfig to anywhere that needs it.

This avoids multiple methods all taking a similar huge list of arguments.

[rerpha]

do you think it'd make sense to have

A) one struct for the entire howl command's arguments
B) one struct for common args ie. an EventMessageConfig which is used from main -> howl -> produce_messages -> generate_fake_events? It seems inefficient to pass all of the args given to howl to every func down the chain?

[Tom-Willemsen]

I was thinking both, but you could combine both approaches by including a EventMessageConfig within a HowlConfig struct