[vector] Removal of some operations

[Paul Sandoz]

I just pushed a patch that stuffs a bunch of operations in helper classes.

Paul.

> On Feb 2, 2018, at 1:46 PM, John Rose <john.r.rose at oracle.com> wrote:
> 
> On Feb 2, 2018, at 5:38 PM, Paul Sandoz <paul.sandoz at oracle.com <mailto:paul.sandoz at oracle.com>> wrote:
>> 
>> 
>> 
>>> On Feb 2, 2018, at 6:29 AM, John Rose <john.r.rose at oracle.com <mailto:john.r.rose at oracle.com>> wrote:
>>> 
>>> On Feb 2, 2018, at 1:18 AM, Paul Sandoz <paul.sandoz at oracle.com <mailto:paul.sandoz at oracle.com>> wrote:
>>>> 
>>>> In an effort to shrink down the API to a smaller set of operations and thus make it easier scope out a first viable implementation we can remove the following lesser known operations:
>>> 
>>> Rather than complete removal, I think it would be better to
>>> sideline those operations into a separate class, as static
>>> generic algorithms.
>>> 
>>> Maybe the *Exact guys could go into one class.  And
>>> eventually a set of *Saturating algorithms, alongside it.
>>> 
>> 
>> The intent being these are helper methods that are not necessarily optimized but might in the future and if so are candidates to be promoted to the Vector* classes? (and since this is incubating we still have flexibility to remove ‘em)
> 
> Correct.  Back-benchers.
> 
>> (Also, does it really say "substract”?
>> 
>> No, that was a typo originating from the list i copied from and failed to correct in this email.
>> 
>> Paul.
>