Hello Interesting question
From my point of view, I want to parse a huge file without loading it in memory... Maybe something worth the reading https://developer.apple.com/library/ios/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/TechniquesforReadingandWritingCustomFiles/TechniquesforReadingandWritingCustomFiles.html Gérard Le 20 mai 2016 à 13:59, Maury Markowitz via swift-users <swift-users@swift.org> a écrit : >> On May 20, 2016, at 4:16 AM, Quinn The Eskimo! via swift-users >> <swift-users@swift.org> wrote: >> I disagree. One-shot file system APIs make sense for a lot of reasons: > > I do most of my programming in .Net, where streams are the primary IO system. > Even simple tasks often require multiple objects and loops copying data > between them. Limitations in the API and in the implementations layer on > complexity. > > I relish whenever I have to do IO on the Mac using the one-shot API. A single > line of code almost always accomplishes what I want, and the API is perfectly > clear on what it's doing. > >> I generally find myself streaming through a file only when I’m dealing with >> some sort of I/O pipeline, which is the exception rather than the rule. > > Indeed, and in these domain's it's an excellent conceptual platform to work > in. But as the *primary* API it's a wonderful example of distributed cost. > > _______________________________________________ > swift-users mailing list > swift-users@swift.org > https://lists.swift.org/mailman/listinfo/swift-users _______________________________________________ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users
