<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>It had to be merged from Apple’s upstream changes, as pointed out at the start of this thread, so the feature requires compiler integration. It’s likely the same work was done in clang/llvm for the C-based language side of things. Even if it’s an Apple-only feature (as this index format seems Apple specific, according to the comments in the merged PR), once it touches the compiler, development should be done in the open and not as upstream dumps, IMO. Otherwise things can get out of sync pretty badly.<div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Jon<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 4, 2017, at 11:21 PM, Jonathan Prescott <<a href="mailto:jprescott12@icloud.com" class="">jprescott12@icloud.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I think the indexing while building is really part of Xcode and not Swift since it also works on C, C++, Obj-C and Obj-C++. It’s not just for Swift.<div class="">Jonathan</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jul 4, 2017, at 11:18 PM, Jon Shier <<a href="mailto:jon@jonshier.com" class="">jon@jonshier.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>The feature this thread is about, indexing while building. I’m of the opinion that, if a feature needs to be integrated with the Swift compiler, as this one was, development of that integration should be done in the open. Perhaps I misunderstand how this feature is separated between the compiler and higher level tools, but avoiding a month long mismatch between the open source and Apple versions, one which prevents open source snapshots from working in Xcode at all, is a good thing, no?<div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Jon<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Jul 4, 2017, at 11:14 PM, Jonathan Prescott <<a href="mailto:jprescott12@icloud.com" class="">jprescott12@icloud.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I’m curious what Swift features you think Apple is developing internally that is not being done concurrently as part of, or totally within, the open-source project. To me, everything that is the compiler(s), debugger, standard librarIes, package manager are all being constructed completely within the open-source community (both LLVM/CLang and Swift). All of the Xcode pieces you explicitly mentioned (the source code editor, the build system, for example) are all part of the Xcode application, and should be developed by Apple as part of their product offering to whatever level of privacy they desire. And, the iPad Playgrounds Application is Apple-proprietary as well.<div class=""><br class=""></div><div class="">What components/Swift features are you concerned about?</div><div class=""><br class=""></div><div class="">Just asking.</div><div class=""><br class=""></div><div class="">Jonathan</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jul 4, 2017, at 9:20 PM, Jon Shier via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Xcode 9 fixes my biggest complaint about Xcode, which was the text editor. The new one, based off the one used in the Playgrounds iPad app, is far better in pretty much every way than the old one. It’s still missing features (which should be added by release) but I use it as much as I can. It still suffers from some of the same issues as the old editor, namely that its functionality breaks almost completely when SourceKit crashes, which is really annoying for stuff like syntax highlighting and auto indentation, since it seems like that stuff shouldn’t break when that happens. But it recovers a bit better now from those situations. The new build system is also really nice, though largely invisible.<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>I do find it concerning that Apple is developing Swift features internally, which is rather antithetical to open source development and leads to painful transition periods like this where Apple’s version and the open source version are out of sync. It really doesn’t seem necessary for these features to be developed privately. I would hope the Swift project takes a more WebKit-like approach to these features, where all features are developed in the open source branch, with only the SPI integration private to Apple. Features like the content filters shipped last year were fully visible in the open source tree long before WWDC. It would be better for Swift to develop all of these features in the open.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Jon<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Jul 4, 2017, at 9:05 PM, David Baraff via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">How is xcode9 beta going in general? I would dearly love to start using the new Codable stuff, and I don’t have to really worry about swift 3 compatability — it’s just a question of the xcode 9 beta being safe enough to get work done.<div class=""><br class=""></div><div class="">(The fact that “yank” was broken makes it a non-starter for me but i’m kind of hoping it gets fixed soon.)</div><div class=""><br class=""><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jul 4, 2017, at 6:02 PM, Anders Hasselqvist via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi,<div class=""><br class=""></div><div class="">I've been trying to use the swift4 snapshot toolchains with Xcode9 beta with little success.<br class=""></div><div class=""><br class=""></div><div class="">When building I get the error:<br class=""></div><div class="">"</div><div class=""><span style="font-family:Menlo;font-size:11px" class=""><unknown>:0: error: unknown argument: '-index-store-path'</span></div><div style="margin: 0px 0px 0px 12px; font-size: 11px; line-height: normal; font-family: Menlo;" class="">Command /Library/Developer/Toolchains/swift-4.0-DEVELOPMENT-SNAPSHOT-2017-06-29-a.xctoolchain/usr/bin/swiftc failed with exit code 1</div><div class="">"</div><div class=""><br class=""></div><div class="">I believe that this because of missing "indexing while building" support in the open source swift in the currently available snapshots. (The feature was merged just a few days ago: <a href="https://github.com/apple/swift/pull/10726" class="">https://github.com/apple/swift/pull/10726</a>)</div><div class=""><br class=""></div><div class="">Is there a way to disable "indexing while building" in Xcode9?</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Anders</div><div class=""><br class=""></div></div>
_______________________________________________<br class="">swift-users mailing list<br class=""><a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-users" class="">https://lists.swift.org/mailman/listinfo/swift-users</a><br class=""></div></blockquote></div><br class=""></div></div></div>_______________________________________________<br class="">swift-users mailing list<br class=""><a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-users" class="">https://lists.swift.org/mailman/listinfo/swift-users</a><br class=""></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">swift-users mailing list<br class=""><a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-users" class="">https://lists.swift.org/mailman/listinfo/swift-users</a><br class=""></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>