Security News
38% of CISOs Fear They’re Not Moving Fast Enough on AI
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
github.com/mauricioklein/go-chainable
Provides an easy and convenient way of chaining function calls in Golang, with support to argument's feedback and error-handling
go get github.com/mauricioklein/go-chainable
It's common to find Go programs similar to the one below:
x, err := sum2(2)
if err != nil {
return 0, err
}
y, err = mul2(x)
if err != nil {
return 0, err
}
z, err = div2(y)
if err != nil {
return 0, err
}
return z, nil
Error handling can make the codebase messy. At the same time, chaining function calls can obfuscate errors and cascading calls can increase the cognitive complexity.
Elixir
, F#
and other languages solve this problem with the support to pipes, but Golang hasn't such
feature.
Chainable provides a clearer way to chain function calls, using the output of the previous function as the input of the next one.
The example above could be re-written using Chainable as follow:
import (chainable "github.com/mauricioklein/go-chainable")
res, err := chainable.New().
From(2).
Chain(
sum2,
mul2,
div2,
).
Unwrap()
// "Unwrap" returns the result as a slice of Argument, matching the return values
// of the last function. So, we just need to cast them to the correct type
z := res[0].(int)
Another advantage is that Chainable automatically handle errors in a chain.
Thus, if one of the methods returns an error as the last argument, the chain is broken and the error is returned by the "Unwrap" method:
raiseError := func () (int, error) { return 0, errors.New("generic error") }
plus2 := func (x int) { return x + 2 }
chainable.New().
Chain(raiseError). // breakes the chain
Chain(plus2). // never called
Unwrap() // returns nil, "a generic error"
If automatic error handling isn't desired (i.e. the error should be chained along with the other arguments), the method "ChainDummy" should be used instead of "Chain" (pay attention that the next function in the chain must be able to receive the error generated by the previous one):
raiseError := func () (int, error) { return 2, errors.New("generic error") }
plus2AndError := func (x int, e error) (int) { return x + 2 }
chainable.New().
ChainDummy(raiseError).
Chain(plus2AndError).
Unwrap() // returns []Argument{4}, nil
"Chain" and "DummyChain" methods are variadics, and can be used in conjunction:
chainable.New().
Chain(f1). // error handling enabled for f1
ChainDummy(f2). // error handling disabled for f2
Chain(f3, f4). // error handling enabled for f3 and f4
Unwrap()
Finally, to reset a chain and make it ready to be reused, just call the method "Reset":
chain := chainable.New()
// ... use of chain
chain.Reset()
git checkout -b my-new-feature
)git commit -am 'Add some feature'
)git push origin my-new-feature
)FAQs
Unknown package
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.
Security News
Company News
Socket is joining TC54 to help develop standards for software supply chain security, contributing to the evolution of SBOMs, CycloneDX, and Package URL specifications.