Live Swift playground in Bing search results
This was a pleasant surprise: I’m not sure how useful it is, since I don’t typically turn to a search engine to run random Swift code, but hey, kudos for effort.
This was a pleasant surprise: I’m not sure how useful it is, since I don’t typically turn to a search engine to run random Swift code, but hey, kudos for effort.
Input code: Push button. Expect results (or at least bacon). Get: Foo.swift:76:21: error: expected ‘,’ separator .day: { String($0 + 1) }, ^ , Foo.swift:76:21: error: expected expression in list of expressions .day: { String($0 + 1) }, ^ Foo.swift:76:21: error: expected ‘,’ separator .day: { String($0 + 1) }, ^ , Believe it or… Read more
Foo.swift:75:49: error: expression was too complex to be solved in reasonable time; consider breaking up the expression into distinct sub-expressions let componentsOfPotentialInterest = [(Calendar.Component, ((Int) -> String))]( ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The fuck?
I run Einstein@Home, using both CPU cores & my GPU. Other than a few month period where Einstein@Home was issuing broken GPU work units, I’ve been successfully doing this for years, I think. Longer than I can really remember, in any case. It appears, however, that 10.12.2 has introduced some serious issues impacting those GPU… Read more
Thanks to one of the genuine upsides of Swift, full Unicode support in the compiler itself, you can do: Finally you can express yourself honestly within your program: Or, if you prefer to be polite & British about it: You can go further, if you like, and have all manner of interesting things thrown about… Read more
You can readily tell that Swift was created by a C++ fanatic, by its fucking obtuse error messages. ⤹ Me Swift compiler ⤵︎ In today’s episode of “what the fuck do you want, compiler?”, we tackle: foo.swift:186:39: error: ambiguous reference to member ‘joined()’ log.debug(“\(thingies.joined(separator: “, “))”) ^~~~~~~~ Swift.BidirectionalCollection:27:17: note: found this… Read more
Result? Explode: Error Domain=NSCocoaErrorDomain Code=4 “The folder “sigh.txt” doesn’t exist.” UserInfo={NSFilePath=~/Desktop/sigh.txt, NSUserStringVariant=Folder, NSUnderlyingError=0x1018110b0 {Error Domain=NSPOSIXErrorDomain Code=2 “No such file or directory”}} And since there’s no documentation on that write() method, and this is obviously a perfectly reasonable request that can’t sanely yield that bizarre error message, you could be forgiven for having no idea how… Read more