Bug 27858 - dispatch_object_t should be mapped to CoreFoundation.DispatchObject
Summary: dispatch_object_t should be mapped to CoreFoundation.DispatchObject
Alias: None
Product: Objective Sharpie
Classification: Desktop
Component: General ()
Version: 2.0.3
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Aaron Bockover [MSFT]
Depends on:
Reported: 2015-03-10 20:35 UTC by Dave Dunkin
Modified: 2015-03-11 01:47 UTC (History)
0 users

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 Dave Dunkin 2015-03-10 20:35:05 UTC
dispatch_object_t and related should map to the types in CoreFoundation instead of NSObject<OS_dispatch_object>.

Example below from AFNetworking:

		// @property (nonatomic, strong) dispatch_queue_t completionQueue;
		[Export ("completionQueue", ArgumentSemantic.Strong)]
		NSObject<OS_dispatch_queue> CompletionQueue { get; set; }

		// @property (nonatomic, strong) dispatch_group_t completionGroup;
		[Export ("completionGroup", ArgumentSemantic.Strong)]
		NSObject<OS_dispatch_group> CompletionGroup { get; set; }
Comment 1 Aaron Bockover [MSFT] 2015-03-11 01:47:22 UTC
Fixed. I'm sure there are a lot of types like these which don't map name-for-name in our product bindings. We'll have to fix them on a case-by-case basis. I'll try to solicit a volunteer to perform an audit at Xamarin.