I've fast-forwarded the pull request branch to Proposal 1b, so you can review!
1b replaces
Option<SetPointStruc>in which the Some() variant, as must be the case, has a single item payload which is a struct with spec and value, by basically a roll-our-own option in which…
On Thursday (February 20), we decided to implement a variant of Proposal 1, which we called Proposal 1a. The idea was to make the set point an…
It also forces client code to unwrap an Option, even when they know, because they checked in the sanctioned way, that there is a set point.
That's a good point: the assembly module's…
Single source of truth about whether there's a set point
The simplification is precisely: only having one way to check whether there is a set point.
I agree that it would be good to…
For the design to be maintainable in the long run, there can only be one authoritative location of the truth of what a Regulator is set to. […] Therefore, any f64 accessible from a Regulator…
Setting regulators' private fields
Am I more or less correct in thinking of the pub items in the Regulator struct as the public member data [fields], the other items in the Regulator…
I've now implemented this behavior change in a way that I think is consistent with our meeting discussions on February 13…
Regulator
Yes, I think it should be renamed once #48 is merged. At that point, we could change the description to say "as of #48" and update to the terminology of #48.
Addressed by pull request #34, which adds examples/kaleidocycle.rs for confirmation.