![]() ![]() Maybe it is worth to file a bug on func <=(String, String) being locked down to a specific sorting behavior, but my guess is that this is intentionally vague to support different implementations. /rebates/&252fsorted-3-for-mac. ![]() If you need some specific ordering, you need to be more precise. The String <= String operation is ambiguous in the first place. Pure luck I'd say, do not rely on itīut most importantly: why do you assume this is stable in the first place. The file named 'sorted-yyyyMMdd-hhmmss.sorted3' that you can directly see now is the file you exported through Manual Backup, and the file in the 'Auto' folder is the file exported through Auto Backup. Tap the folder of the device you want to view, and then open the 'Backups' folder. And this is probably because the Foundation implementation is the same. You can go to ' '>'System Preferences'>'Sharing' to check the name of your Mac. The more interesting question is why "pare" works the same (which is not in the stdlib, but in Foundation). Sorted combines your tasks, calendar events and notes into a unified timeline so you can hyper-schedule your entire day in one place. And they probably chose to implement it differently (my guess: macOS just using and tuxOS using ICU or maybe plain strcmp, ask GitHub -) ) As far as I can see the semantics of func <=(String, String) do not seem to be documented/fixed (also the language guide doesn't mention it). I'd say because there are two (different) implementations of the stdlib for Linux and macOS. This has nothing to do with "Server" and the general Swift forum will likely give you a better explanation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |