[Octave-bug-tracker] [bug #47416] call of overloaded 'octave_value(Array<int>&)' is ambiguous

[Mike Miller]

Update of bug #47416 (project octave):

                  Status:               Confirmed => Wont Fix               

    _______________________________________________________

Follow-up Comment #8:

I want to say this is invalid and should be closed as won't fix, but leaving
open for now for other opinions.

There actually is no constructor for octave_value(const Array<int>&), there is
only a constructor that takes an Array<octave_idx_type>. If octave_idx_type is
not exactly "int", then it fails to construct and shows the full list of other
constructors that one Array<> type may be converted (via copying) into another
Array<> type.

There are valid constructors for all of the sized integer types that Octave
uses, so those should be used instead, or octave_idx_type if the values being
returned are actually indices into an Octave array.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47416>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/