You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some wiring spec methods and convenience methods might return errors, but it is tedious and verbose to expect a wiring spec to check error return values for all wiring spec calls.
The golang suggested alternative approach can be used here; we can accumulate errors in the blueprint.WiringSpec. Then to do error checking, the wiring spec can provide a method Err() to return any accumulated error(s). For wiring specs, this means they can do error checking, but without verbose error checking.
The text was updated successfully, but these errors were encountered:
In GitLab by @JonathanMace on Sep 20, 2023, 22:42
Some wiring spec methods and convenience methods might return errors, but it is tedious and verbose to expect a wiring spec to check error return values for all wiring spec calls.
The golang suggested alternative approach can be used here; we can accumulate errors in the blueprint.WiringSpec. Then to do error checking, the wiring spec can provide a method Err() to return any accumulated error(s). For wiring specs, this means they can do error checking, but without verbose error checking.
The text was updated successfully, but these errors were encountered: