Bug 58092 - CoreML.MLFeatureValue.Type property is confusingly named
Summary: CoreML.MLFeatureValue.Type property is confusingly named
Status: RESOLVED DUPLICATE of bug 58094
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 10.99 (xcode9)
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2017-07-12 01:22 UTC by Larry O'Brien
Modified: 2017-07-12 20:03 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 Larry O'Brien 2017-07-12 01:22:44 UTC
To avoid confusion, I think CoreML.MLFeatureValue.Type should be named `MLFeatureType` or `FeatureType`. The MLFeatureValue is an immutable value and type where the type is one of MLFeatureType's values.
Comment 1 Vincent Dondain [MSFT] 2017-07-12 20:03:50 UTC

*** This bug has been marked as a duplicate of bug 58094 ***