mirror of https://github.com/mosra/magnum.git
Browse Source
The ambiguity with StridedArrayView1D<const char> was there always, I just didn't hit that anywhere so far. With the recent changes in Corrade, where StridedArrayView2D<const T> is constructible from StridedArrayView1D<T> as well in addition to const T, the ambiguity gets hit by a test. So test both variants and add an overload that resolves those. There's no other such case in either MeshIndexData or SceneFieldData, as the StridedArrayView1D<const void> and StridedArrayView2D<const char> constructor variants always have differing arguments. Neither it happens in case of (ARM) platforms where char is unsigned.pull/651/merge
2 changed files with 40 additions and 0 deletions
Loading…
Reference in new issue