@dextero I want this to land before #84

Nice idea! rustfmt still needs to be ran and I think that should be(come) a requirement in the CI?

EDIT: I didn't really vet the changes at all but trust you moved it completely - CI is happy so the imports / module references should all be good.

I have added basic rustfmt config. Other PRs can take care of that if that's important.
I tried to leave the public facing api exactly the same. Later the better names could be found for modules if necessary, but the single file was getting unwieldy.

I have added basic rustfmt config. Other PRs can take care of that if that's important.

Oh I didn't need a rustfmt.toml config; if anything the edition set now should by default be fetched from Cargo.toml?

I meant running it in CI to reject changes if they don't adhere to the (default!) formatting standard, instead of causing unnecessary reformatting churn later on.

I have added basic rustfmt config. Other PRs can take care of that if that's important.

Oh I didn't need a rustfmt.toml config; if anything the edition set now should by default be fetched from Cargo.toml?

I meant running it in CI to reject changes if they don't adhere to the (default!) formatting standard, instead of causing unnecessary reformatting churn later on.

It's ok I formatted with rustfmt now :)

Oh yeah I trust that you formatted it now, just thinking it'd be nice to validate this in CI going forward for future contributions and pushes, as done in #86 :)