3 ms·
"Side effect" in my comment means an unintended side effect from an impure functional component (often a case of missing a useEffect, useMemo, or useCallback).
by CharlieDigital 4y ago
"Side effect" in my comment means an unintended side effect from an impure functional component (often a case of missing a useEffect, useMemo, or useCallback).
- bayesian_horse 4y ago"Side Effect" in functional programming usually means the function is affecting something other than the output. And calling a hooks really doesn't, they just output the description of such an effect on a side channel.
- CharlieDigital 4y ago> usually means the function is affecting something other than the output That's exactly the point. If you leave an errant function call in a functional component, it's going to affect something other than the output of that component.