Bug 14125 - NSDictionary ValueForKey and SetValueForKey methods should accept any NSObject as a parameter
Summary: NSDictionary ValueForKey and SetValueForKey methods should accept any NSObjec...
Status: RESOLVED INVALID
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 6.4.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-08-20 19:26 UTC by Timothy Risi
Modified: 2013-08-20 20:03 UTC (History)
2 users (show)

Tags:
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:
Status:
RESOLVED INVALID

Description Timothy Risi 2013-08-20 19:26:38 UTC
The ValueForKey and and SetValueForKey methods on NSDictionary (And NSMutableDictionary as well) only accept an NSString for the key parameter.  An NSDictionary can have any NSObject as a key, not just an NSString, so you are unable to access anything using a non-NSString key.

Xamarin.iOS 6.4.1.1
Comment 1 Sebastien Pouliot 2013-08-20 20:03:25 UTC
There's an indexer that accept an NSObject instance (beside the one for string and NSString) so:

    dict [new NSObject ()] = new NSObject ();

is possible today and much more nicer looking, source wise, that using `ValueForKey`. 

FWIW `ValueForKey` comes from `NSObject` not `NSDictionary`.