-
Notifications
You must be signed in to change notification settings - Fork 38
Comparing changes
Open a pull request
base repository: uber/swift-concurrency
base: v0.6.3
head repository: uber/swift-concurrency
compare: master
- 11 commits
- 28 files changed
- 4 contributors
Commits on Dec 10, 2018
-
Configuration menu - View commit details
-
Copy full SHA for 7ead5bc - Browse repository at this point
Copy the full SHA 7ead5bcView commit details
Commits on Dec 13, 2018
-
Fix AtomicInt usages of deprecated atomic APIs (#26)
* Fix AtomicInt usages of deprecated atomic APIs As of iOS 10.0 and MacOS 10.12 the old `OSMemoryBarrier`, `OSAtomicCompareAndSwap64Barrier`, `OSAtomicIncrement64Barrier`, and `OSAtomicDecrement64Barrier, APIs are deprecated. The warnings suggested new APIs are C++ and are not accessible from Swift. `OSMemoryBarrier` can be directly replaced with `atomic_thread_fence(memory_order_seq_cst)` which is accessible from Swift. The rest of the suggested C++ APIs `atomic_fetch_add`, `atomic_fetch_sub`, and `atomic_compare_exchange_strong` are not accessible from Swift. This change creates a Objective-C wrapper for these C++ APIs, so Swift code can access them. * Update TravisCI to use Xcode 10.1
Configuration menu - View commit details
-
Copy full SHA for 9c2d8fb - Browse repository at this point
Copy the full SHA 9c2d8fbView commit details
Commits on Dec 14, 2018
-
Configuration menu - View commit details
-
Copy full SHA for efbd273 - Browse repository at this point
Copy the full SHA efbd273View commit details
Commits on Jan 24, 2019
-
Allow task execution to throw errors (#28)
* Allow task execution to throw errors Adds support to allow task execution to throw errors. The error is then reported back via the `SequenceExecutionHandle.await` method when results are being retrieved. * Ignore SPM generated scheme * Xcode project changes
Configuration menu - View commit details
-
Copy full SHA for d132096 - Browse repository at this point
Copy the full SHA d132096View commit details
Commits on Feb 20, 2019
-
Add AutoReleasingSemaphore (#30)
Similar to `DispatchSemaphore`, `AutoReleasingSemaphore` is a synchronization mechanism that ensures only a set number of threads can concurrently access a protected resource. Unlike `DispatchSemaphore`, `AutoReleasingSemaphore` auto-releases all blocked threads when the semaphore itself is deallocated.
Configuration menu - View commit details
-
Copy full SHA for c773c32 - Browse repository at this point
Copy the full SHA c773c32View commit details -
Signal concurrency limiting semaphore when task errors (#31)
This fixes the issue where if a task throws an error during execution, the concurrency limiting semaphore is never signaled. This can hault the entire sequence since no new tasks can continue execution.
Configuration menu - View commit details
-
Copy full SHA for 60edf0a - Browse repository at this point
Copy the full SHA 60edf0aView commit details -
Update ConcurrentSequenceExecutor to use AutoReleasingSemaphore (#33)
* Update ConcurrentSequenceExecutor to use AutoReleasingSemaphore Fixes #29 * Remove debugging code
Configuration menu - View commit details
-
Copy full SHA for e29e42c - Browse repository at this point
Copy the full SHA e29e42cView commit details
Commits on Apr 5, 2019
-
Configuration menu - View commit details
-
Copy full SHA for ccb4866 - Browse repository at this point
Copy the full SHA ccb4866View commit details
Commits on Oct 2, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 12c7233 - Browse repository at this point
Copy the full SHA 12c7233View commit details
Commits on Oct 3, 2019
-
Configuration menu - View commit details
-
Copy full SHA for 9b1a09d - Browse repository at this point
Copy the full SHA 9b1a09dView commit details
Commits on Mar 17, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 648aaec - Browse repository at this point
Copy the full SHA 648aaecView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.6.3...master