In the Absent case, it's the 0th tuple entry of the payload. In the Present case, it's the spec field of the payload.
If you find it less disorienting, we could do this:
pub enum…
[…] if I already have a SpecifiedValue, is there a way to make it the set_point of a Regulator? Perhaps there should be […]
Yes, I think we should add a set method for this as soon as…
I think it's best to keep Husht as close as possible to Rust in terms of features, for two reasons.
- If a proposed Rust feature gets adopted by Husht but not by Rust, there's a danger that…
To me, it seems perfectly natural to have this:
pub enum SpecifiedValue {
Absent(String),
Present {
spec: String,
value: f64
}
}
An absent…
Yes, I'll do this—I was just waiting for a go-ahead from you. I should've mentioned that in the last comment.
Or do you just want to defer this issue until after we switch to a view in which elements and regulators are viewed in a more egalitarian fashion?
Yes: the issue becomes moot if we ditch the…
The most convenient place to see a curvature regulator might be in-line with the display of its subject element. So perhaps we need a hybrid of unary regulators in the element list and poly-ary…
I think I've finished responding to this comment and addressing or responding to all the code-level comments. Please review again at your convenience! I'll be working on #64…
More immediately pertinent, but inspired by (4) because likely we will need to address it at least by the time we implement (4): it's counterintuitive/asymmetric that I can select an element but…
Need to file an issue to allow removal of entities, regulators and/or elements.
Done (#62).
The current optimization seems to prefer changing curvature over position […]
I've brought this up in issue #61.
If you add an inversive distance regulator between A and B, and then add one between A and C, and then select B and C and add a regulator, presuming that neither of the dropdowns for B or C is…