> I’m a little concerned that someone somewhere is relying on sharing a > mutable SortField, so I’d be careful about making a change like that. At > least, add an mx_internal flag to get back old behavior so if someone does > complain they have a way of recovering.
Great idea. In the end I decided to go for a three-step process: 1) marking the setters and reverse() functions as deprecated (in v4.15) - complete 2) placing them behind mx_internal (which includes renaming them) and making reverse() work with immutable Sort and SortField objects (in v4.16 - could you please create this version tag in Jira?) 3) completely removing the state setters (in 4.17) This way people can have more time to adapt to the changes.
