Bug 26749 - 8.6 unified api: vImageBuffer.Width/Height/BytesPerRow are not nint
Summary: 8.6 unified api: vImageBuffer.Width/Height/BytesPerRow are not nint
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 8.6.0
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-02-04 14:23 UTC by softlion
Modified: 2015-02-05 08:36 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description softlion 2015-02-04 14:23:47 UTC
And the decompiled code is ... very strange.
Look below.
Width is int, but setter casts it to nint.

namespace Accelerate
struct vImageBuffer:

    private nint HeightIntPtr;
    private nint WidthIntPtr;
    private nint RowBytesCountIntPtr;
    public int Width
        return (int) this.WidthIntPtr;
        this.WidthIntPtr = (nint) value;

Comment 1 Rolf Bjarne Kvinge [MSFT] 2015-02-05 08:00:15 UTC
This is by design; it is highly doubtful you'll ever need Height/Width/BytesPerRow > int32.MaxValue, so we've bound it using the 32-bit data types.
Comment 2 softlion 2015-02-05 08:36:39 UTC
why didn't Apple thought of this then ?

You are creating a potential limitation to Apple's version because you decided to.
If tomorrow Apple's decide to put specific information in the unused high bits of the 64 bit value, what will happen ? Your customers will be stuck until you fix it.

This is not a good direction to follow.