Dynamic Codegen in Rust with Daedalus

[harrison-e]

Changes

Daedalus:

• Replaces the Python format string codegen from Embedded-Base/cangen with Rust proc macros
• Generates decode functions, decode master mapping, encode functions, encode master mapping, encoder key list, and simulate function body, based off of CAN spec in Embedded-Base/cangen/can-messages, with a single macro call in src/decode_data.rs, src/encode_data.rs, and src/simulate_data.rs respectively.

Cangen:

• Replaces the Python datatypes from Embedded-Base/cangen with equivalent Rust structs
• Contains helper traits for Daedalus

Calypso:

• decode_data.rs, encode_data.rs, and simulate_data.rs are now generated with Daedalus macros. Since they're only 5 lines (pre-expansion), I've begun tracking them.
• Master mappings are now phf hash maps, instead of a struct wrapping a giant match function.
• FormatData struct is no longer dynamically generated in format_data.rs. Instead, is now hardcoded in data.rs, and format_data.rs is removed. I hardcoded this since I assume that it will change very rarely. In the event that a new format is added, though, it will need to be added to data.rs.
• Changed main.rs to work with Daedalus-generated code.
• Added new dependencies to Cargo.toml and Cargo.lock.
• Removed calypsogen.py and its call in build.rs.
• Removed deprecated exports from lib.rs.
• Removed deprecated files from .gitignore.

Test Cases

• Tested with mosquitto, mqttui, and cansend, working as expected
• Tested with cargo run --bin simulate, working as expected

To Do

Any remaining things that need to get done

• switch to new CAN typing (acquiesce NetField and CANPoint)

Checklist

It can be helpful to check the Checks and Files changed tabs.
Please reach out to your Project Lead if anything is unclear.
Please request reviewers and ping on slack only after you've gone through this whole checklist.

• No merge conflicts
• All checks passing
• Remove any non-applicable sections of this template
• Assign the PR to yourself
• Request reviewers & ping on Slack
• PR is linked to the ticket (fill in the closes line below)

Closes #53

[jr1221]

Will approve once tested Sunday. Really really cool. I do see room for improvement by deviating from how the python used to look and getting dynamicly into the bitreader logic a little more, but that is a task for a future PR.

[jr1221]

Running cargo clippy locally can show u anything the CI linter will fail on.