match expressions
Suppose you add an i.d. regulator to A and B, and set it to 2, and then it one of its input boxes (say with both showing), replace the set point with a and hit enter. You get an error indicator…
Another hard-to-discover keyboard control: pressing escape to reset a regulator input. This came up during review of #48.
I definitely think we should give the Absent variant a specification field if we end up with more than one way to specify absence. However, I'm not sure it makes sense to add that field now. It…
Nice catch! I've changed "above" to "at" to resolve the ambiguity (7cbd926). Does that read all right to you?
I've added a comment to this effect (7cbd926). Let me know if I should make it more detailed.
Good point! I've made insert_regulator private for now (c368a38).
Specified values and assemblies do seem like pretty independent concepts, so putting SpecifiedValue in its own module might be reasonable.
Several enums from the standard library have similar methods.
Option:is_some/ [is_none](https://doc.rust-lang.or…
Or doesn't the Regulator already have a ReadSignal for its SpecifiedValue?
Yes: the set_point field is public. Thus, there's no need for try_set to return something that gives you access…
I think tuples are designed with arbitrary combinations of types in mind, so I'd be surprised to find utility methods to broadcast over tuples of the same type—and indeed, I haven't managed to…
I take it the .with method is how we manipulate the "payload" (or whatever the correct term is) that is wrapped by a Signal?
Yes: [with](https://docs.rs/sycamore/latest/sycamore/reactive/str…
The declaration
use SpecifiedValue::*;
puts all variants in scope. I currently have it just after the definition of SpecifiedValue, because it felt out of context elsewhere. For…
We could indeed modify try_set so that it returns a clone of the Result<SpecifiedValue> computed from the given specification. This might be useful if the caller wants a detailed error report…