Equals for Units

[Owen Arnold]

You currently have to compare units on the basis of ID, Would be nice to have member and non-member Equals operators to do this comparison.

[Nick Draper]

Moved to release 2.4

[Nick Draper]

Moved at the code freeze for release 2.4

[Nick Draper]

Moved to r2.6 at the end of r2.5

[Nick Draper]

Moved to the Backlog after the code freeze for R2.6

[Nick Draper]

bulk move to assigned at the into of the triage step

[Dan Nixon]

Added equality and inequality opertors to Unit

Refs #5977

Changeset: c4676565738ebcd1e44ea7beca7c820497a25ef7

[Dan Nixon]

Added equality and inequality operators (==, !=) to Unit base class and unit tests for both operators.

[Martyn Gigg]

The changes to the UnitTest test have caused some memory leaks that are shown in the valgrind checks: ​http://builds.mantidproject.org/view/Valgrind/job/valgrind_develop_core_packages/95/valgrindResult/pid=10104,0x7/

The pointers returned from the .clone() methods just need to delete the returned pointers.

As a point of style concerning auto: It should only give the type and a pointer or reference should still include * or & to signify this. So the energy clone line would be

auto *e1 = Energy().clone();

then the delete further down.

[Dan Nixon]

Fixed issues mentioned in two further commits (which don't seem to be showing here).

[Peter Parker]

Dan, one of the commits contained "Refs #5799" instead of 5977. No idea where the other one went, as that had the correct ticket number. Both have been correctly published and checkbuilt, though.

[Martyn Gigg]

Merge remote-tracking branch 'origin/bugfix/5977_unit_equals_operator'

Full changeset: ​28ce74287b0479020134953fbf9ae6865ed08b10

[Stuart Campbell]

This ticket has been transferred to github issue ​6823