Standardize pattern for controlling optional Outputs
- Dominant language
- Dart
- Stars
- 115
- Forks
- 39
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 1
Description
### Motivation
In some components we want optional outputs that also cause different behavior in the component. A good example is whether we want a 1s complement adder to add the carry-out to the final sum or to leave it as a carry-out and produce sum-1.
### Desired solution
Two solutions are immediately apparent: Supply only a boolean that causes a similarly named output to be added and behavior modified, or supply a nullable Logic? which causes the different configuration and is assigned the new output value (which requires an actual output be added and connected to the passed in Logic).
### Alternatives considered
_No response_
### Additional details
_No response_
Contributor guide
Research direction
Start by comparing the two optional-output approaches described in the issue and inspect existing component patterns for optional outputs. The issue names no files or tests; the work is done when one standard is selected and its effect on the optional output and component behavior is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100