If we solved a small independent component of the full problem, then we can
in most situation fix the solution on this subspace.
Note that because there can be more than one optimal solution on an
independent subproblem, it is important to do that in a locked fashion, and
reject future incompatible fixing.
Returns a new id to be used in GetChangedBounds(). This is just an ever
increasing sequence starting from zero. Note that the class is not designed
to have too many of these.
Reports a set of locally improved variable bounds to the shared bounds
manager. The manager will compare these bounds changes against its
global state, and incorporate the improving ones.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-08-06 UTC."],[[["The `SharedBoundsManager` class in C++ manages variable bounds in a parallel processing environment for constraint programming."],["It allows workers to share and update bounds on a set of variables, facilitating the exchange of information between them."],["Workers can report improved bounds, retrieve changes, and synchronize their knowledge of the global bound state."],["It provides mechanisms to fix variables based on solutions of subproblems, ensuring consistency across parallel tasks."],["The class utilizes methods like `ReportPotentialNewBounds`, `GetChangedBounds`, and `Synchronize` for these functionalities."]]],[]]