LagrangeInterpolator has unnecessary copies

[Prof Garth Wells]

LagrangeInterpolator does not uses references for return types where appropriate, and as a result makes numerous necessary copies.

[Chris Richardson]

Looks OK to me - has it been updated? There are still other things which could be better, such as the try/catch clauses, which I don't like.

[Mikael Mortensen]

@garth-wells, could you please be more specific? @chris_richardson, what would you prefer over the try/catch clauses?

[Chris Richardson]

@mikael_mortensen - Function::eval could return a value which would tell you if it was successful or not.

[Mikael Mortensen]

@chris_richardson - Absolutely, just need to keep eval from throwing exceptions.

[Chris Richardson]

Fixes issue #490

→ <<cset f987a6c7e5a5>>

[Martin Sandve Alnæs]

Removing milestone: 1.6 (automated comment)