New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SR-8741] Include CFFileDescriptor in public CoreFoundation source drop #3638
Comments
The exclusion was really only about the lack of libdispatch support in the previous CFLite stuff. There is not much reason to continue to exclude it since we now have the ability to call |
rdar://problem/44425528 |
Comment by Dan Peebles (JIRA) @parkera cool, so it's likely to appear at some point? I can't see the radar link; is that someone else asking for this in the past or just some internal tracking of this request of mine? Is it also appropriate to ask for other similar omissions from CF on this tracker? This one seemed like the most likely to get traction but there are a couple of others that are still missing |
That’s a radar I just filed for you to track this for us internally (a copy of this report). It’ll help us not to lose your request. If you have more requests, you can file them here. Please CC Lily and I as you did here so we get a notification. |
Comment by Dan Peebles (JIRA) Great, I'll do that, and thank you so much! |
No problem, and thank you for the contributions to the project. |
Comment by Dan Peebles (JIRA) Marking the other as a duplicate because this one has made more progress, even though it happened later (and I forgot that the earlier one existed, even though I commented on it a couple of years ago 😛) |
Additional Detail from JIRA
md5: 804e07814a9beb51f8360c9f5ac98c49
is duplicated by:
Issue Description:
The current source seems to jump through some hoops to avoid including it with the REAL_FILE_SCHEDULING preprocessor define and I was wondering if it could just be included in the public repo, since Apple's stance on stuff like this seems to have loosened a bit since the CFLite days.
The reason for this is that I've seen at least a few public projects (https://github.com/facebook/watchman probably the most popular/visible of them that affects me) that use those APIs and we currently have to jump through a bunch of hoops to support them.
Of course, not having seen the actual source I might be missing good reasons to leave it out, but if it was just an oversight I'd love to see it included.
cc @parkera @millenomi who have been involved before with earlier issues like this
The text was updated successfully, but these errors were encountered: