David Vo

Implement embedded_hal::blocking::i2c

1

Doable with what the WPILib HAL exposes, but we'd need to refactor the i2c module.

Depends on (and on top of) #69. [(compare)](https://github.com/auscompgeek/first-rust-competition/compare/raii-dio-pwm...auscompgeek:tristate-dio) Closes: #45

`cargo frc build` to target roboRIO

1

Instead of making teams configure cargo themselves, we should have teams specify the toolchain year, automatically find the toolchain, and build for the correct target. (Having `cargo run` simply run...

Split out dependencies from wpilib-sys

5

wpilib-sys is rather large. The majority of it is just libraries built for athena, most of which the crate doesn't even provide bindings for. The dependencies won't change mid-season, and...

I'm actually not sure what our minimum supported Rust version currently is, but I would like to use `Duration::as_secs_f64` here, which is only stable from Rust 1.38.

The ARMv7 soft-float target seems new in rustc. We should test everything with this target and make sure binaries will run on the roboRIO.

Implement tri-state DIO

5

See wpilibsuite/allwpilib#606 and wpilibsuite/allwpilib@7eab4371f49f4789c171b49b6164a8fb8faf42d0. How might the Rust API look? The dio module will need a refactor, but https://docs.rust-embedded.org/book/static-guarantees/state-machines.html has some nice ideas.

Split out cargo-frc into separate repo?

3

cargo-frc probably won't change much, or as much as the wpilib crate.

Comparison with sphinx-autoapi?

2

This project seems similar to https://github.com/readthedocs/sphinx-autoapi. It'd be nice to have a comparison.