4 ms·
> No overview available. Cool, why is this even posted?
by beervirus 6y ago
> No overview available.
Cool, why is this even posted?
- olliej 6y agoRight? It doesn’t look like any of it is documented?
- samgranieri 6y agoIt's usually like that at first. It'll change later on.
- geerlingguy 6y agoHopefully.
- ChrisMarshallNY 6y agoI'm not holding my breath. I have recently been working with Core Bluetooth (years old), and Swift Package Manager (also long in the tooth), and the documentation for them is still pretty awful. SwiftUI is really bad. In fact, someone has even written a documentation sidecar app for it[0]. I'm spoiled, though. I used to have the full 6-volume set of Inside Macintosh[1]. They don't write 'em like they used to... [0] https://apps.apple.com/us/app/a-companion-for-swiftui/id1485436674?mt=12 https://apps.apple.com/us/app/a-companion-for-swiftui/id1485... [1] https://en.wikipedia.org/wiki/Inside_Macintosh https://en.wikipedia.org/wiki/Inside_Macintosh
- plorkyeran 6y agoSwift Package Manager at least is open source. Unfortunately, digging into the source to find out how to do some incredibly basic thing that any package manager obviously must support and they just haven't documented usually just reveals that they really haven't implemented it.
- saagarjha 6y agoBecause it shipped as part of the SDK in the Big Sur beta today.
- beervirus 6y agoIt’s just a bunch of undocumented class names though.
- saagarjha 6y agoThat's better than Hypervisor.framework was until recently.
- zitterbewegung 6y agoThat’s basically what you can get from apple at this time. They aren’t that motivated for documentation.
- balladeer 6y agoMost of the times when I face a problem on my Mac or iPhone I am surprised to find an official support article by Apple for that problem. But the answer is almost never in that article and then I have to anyway hunt for the answer on the Internet.
- codercotton 6y agoIs there a Docker release for Apple Silicon yet?
- mrpippy 6y agoThe header file likely has comments that didn’t make it into these docs.
- saagarjha 6y agoIt does! (I just picked the first one that I found, the rest also have comments.) $ cat /Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/ System/Library/Frameworks/Virtualization.framework/Headers/VZBootLoader.h // // VZBootLoader.h // Virtualization // // Copyright © 2019 Apple Inc. All rights reserved. // #import <Virtualization/VZDefines.h> NS_ASSUME_NONNULL_BEGIN /*! @abstract Base class of boot loader configuration. @discussion VZVirtualMachineConfiguration requires a boot loader defining how to start the virtual machine. VZBootLoader is the abstract base class of boot loader definitions. Don't instantiate VZBootLoader directly, instead you should use one of its subclasses. @see VZLinuxBootLoader. */ VZ_EXPORT API_AVAILABLE(macos(11.0)) @interface VZBootLoader : NSObject <NSCopying> + (instancetype)new NS_UNAVAILABLE; - (instancetype)init NS_UNAVAILABLE; @end NS_ASSUME_NONNULL_END
- dang 6y agoI put a line break in your file path to prevent the comment from borking the page layout. Sorry. It's a bug we're working on.