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
Desirable because poorly implemented Equals() leads to solvers exceeding maxIter and/or maxNodes, negatively impacting dev workflow.
One possible route is via structs, but this implies a design effort (mutable structs are probably a poor choice; readonly structs will have restrictions impacting action design.
As an alternative, consider providing generic equality and hashing
The text was updated successfully, but these errors were encountered:
eelstork
changed the title
Ease/avoid custom equality and hashing
Equality and hashing defaults
Oct 22, 2019
Desirable because poorly implemented
Equals()
leads to solvers exceeding maxIter and/or maxNodes, negatively impacting dev workflow.One possible route is via structs, but this implies a design effort (mutable structs are probably a poor choice; readonly structs will have restrictions impacting action design.
As an alternative, consider providing generic equality and hashing
The text was updated successfully, but these errors were encountered: