Starlight220
Starlight220
Not sure about `DutyCycle`, but isn't `AnalogPotentiometer` the class the user usually wants?
As the call to `isFinished` is UB itself, whatever we do (or don't do) in the implementation isn't much of importance. For posterity we could check, but it's not violating...
Is it possible with some template magic to have the class support both units and raw doubles?
Clarification: What's the difference between AnalogPotentiometer and this version of AnalogEncoder? It took me some time to realize that `expectedZero` is the offset. I understand that this naming is unambiguous...
> As for the Zero, Naming things is hard. Some people think offset, some think zero. I've seen it about 50/50 split. So whatever the parameter name is, the description...
Mutable requirements (or any other command property) would be a catastrophe. For the use case you're describing, possible solutions are what @PeterJohnson suggested, explicitly including the default holding command in...
I think the answer would be to add an set of interfaces that the `*Publisher` and `*LogEntry` interfaces would inherit from, and then an abstract class/interface that would be subclassed...
> You just described SendableBuilder and SendableBuilderImpl. This is why I think multiple builders is the way to go. There is so much functionality in SendableBuilderImpl beyond this, and duplicating...
Is there value in being able to select from code regardless of sim?
Why do you need to publish the command to the dashboard?