balp

As one more step in learning rust. I have done the Tennis Game Kata. There are a few tradeoff as some names being shorter than optimal, but by that preventing line breaks. That gives better overview.

Is there any rust constructions that would help making the code more readable?

Is there a cleaner solution to get the test parameterized?

Would there be a better fitting rust types for the functions? I started with the interface from Dani Pardo, in Emily Baches refactoring kata.

I started an embedded display for showing sailing (or general boat data) from a SignalK server. Using a target platform of a RasberryPi (3B+) with the old 7" display.

SignalK is a service for handling boat data using a little more modern and distributed protocols that the skipping standards of NMEA-0183 (peer-to-peer serial) or NMEA-2000 (Can bus).

I have made my first Rust library (signalk) to handle the signalk data either over REST or web sockets. On top of that and with frame, egui, and ewebsock I made a GUI that should run in full screen on the raspberry and make it possible to see some of the data inside the boat as well.

I'm quite new to rust as a language, so any feedback would be really helpful. There is a demo running against signalk's demo server on the GitHub pages.