Improve ValidationReport merge behavior

Currently the ValidationReport merge impls create a new MutableValidationReport instance every time and add all the messages from each sub-report to the new report.

A better implementation might be to have a CompositeValidationReport impl that treats sub-reports as a linked-list and provides a 'view' over the top of the sub-reports. Merge operations would become appends to this linked list view.

It would also be good to provide a factory method to ValidationReport that takes a collection of messages. This would mean we could avoid unnecessary merge operations in cases where we perform multiple validations in a single method.

Comments (1)