-
Notifications
You must be signed in to change notification settings - Fork 10
Comparing changes
Open a pull request
base repository: scala-native/scala-native-loop
base: fix-callback-timer
head repository: scala-native/scala-native-loop
compare: master
- 17 commits
- 22 files changed
- 5 contributors
Commits on Jul 27, 2020
-
Fix deadlock on Future waiting for Loop callback (#29)
- `uv_run(loop, UV_RUN_ONCE)` has different semantics than expected. When it returns a number `!= 0` it means that there are still callbacks to be executed but it doesn't mean they are ready now. So there isn't a way to run in non-blocking mode until there are callbacks ready. - The new implementation is hacking the private ExecutionContext queue by using pointer aritmetics to take its value (since it's private). Having the reference to the queue, it's trivial to implement a Eventloop that tries to not starve any of the two eventloops by using a round robin fashion, and avoiding to block until there is anything else to execute.
Configuration menu - View commit details
-
Copy full SHA for 99086a5 - Browse repository at this point
Copy the full SHA 99086a5View commit details -
Configuration menu - View commit details
-
Copy full SHA for dfbd49c - Browse repository at this point
Copy the full SHA dfbd49cView commit details -
Quiet core/test "close multiple times" test (#31)
* Quiet core/test "close multiple times" test As folks may know better than I, in uTest individual tests are documented are documented as returning a value, which can itself be validated. If the return value is not Unit, it is printed out. Before this PR, the "close multiple times" test was returning the value of an object, which was getting printed out and adding something to the log which needed to be figured out as safe. This PR causes that test to be silent, thereby reducing clutter. Agreed, this is a nit. I think it is worth fixing because the present file may serve as a cut & paste template for additional tests as they are added. If I can not fix something useful, I can at least remove a small wart. * Make "close multiple times" return Future Before the timer was timing out after the test was declared successful. To preserve the semantics of utest a async test need to return the last Future to be completed as result Co-authored-by: Lorenzo Gabriele <lorenzolespaul@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 7f9850c - Browse repository at this point
Copy the full SHA 7f9850cView commit details
Commits on Aug 1, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 0c41132 - Browse repository at this point
Copy the full SHA 0c41132View commit details
Commits on Oct 15, 2020
-
Use separate methods for Poll read, write and readWrite (#34)
* Use separate methods for Poll read, write and readWrite * Reintroduce start with dynamic in and out * Bump utest to 0.7.5 * Add PollTests
Configuration menu - View commit details
-
Copy full SHA for 606d020 - Browse repository at this point
Copy the full SHA 606d020View commit details
Commits on Jan 19, 2021
-
Update Scala Native to 0.4.0 (#36)
* Publish 0.1.1 to Sonatype * Update Scala Native to 0.4.0 * Run compile and test on all scala Versions * Fix cross-compile errors
Configuration menu - View commit details
-
Copy full SHA for 1e0eb5b - Browse repository at this point
Copy the full SHA 1e0eb5bView commit details -
Configuration menu - View commit details
-
Copy full SHA for dc94488 - Browse repository at this point
Copy the full SHA dc94488View commit details -
Configuration menu - View commit details
-
Copy full SHA for c75ffd9 - Browse repository at this point
Copy the full SHA c75ffd9View commit details
Commits on Jan 21, 2021
-
Update Utest to com.lihaoyi 0.7.6 (#37)
Fix repository name in ScmInfo
Configuration menu - View commit details
-
Copy full SHA for 9418da4 - Browse repository at this point
Copy the full SHA 9418da4View commit details
Commits on Jan 24, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 2da4a23 - Browse repository at this point
Copy the full SHA 2da4a23View commit details
Commits on Feb 2, 2022
-
* Support Scala 3 * Remove server which doesn't link on Scala 3 - This server is superseded by SNUnit * Add workaround for scala-native#2550
Configuration menu - View commit details
-
Copy full SHA for af3583c - Browse repository at this point
Copy the full SHA af3583cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 87bb475 - Browse repository at this point
Copy the full SHA 87bb475View commit details
Commits on Mar 15, 2022
-
Configuration menu - View commit details
-
Copy full SHA for d44c78b - Browse repository at this point
Copy the full SHA d44c78bView commit details
Commits on Apr 6, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 0886e67 - Browse repository at this point
Copy the full SHA 0886e67View commit details
Commits on Jun 1, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 2af53bc - Browse repository at this point
Copy the full SHA 2af53bcView commit details
Commits on Jun 17, 2024
-
* Scala Native 0.5.x * Upgrade Scala Native version to 0.5.3 * Remove Scala 2.11 support * Fix event loop, use dedicated WorkStealing API instead of unsafe and incorrect reverse-engineering of class structure * Execute CI on stable Ubuntu 22 * nativeConfig ~= {_.withMultithreading(false)} * Replace manual handle memory management with GC allocated space (#2) --------- Co-authored-by: Wojciech Mazur <wmazur@virtuslab.com> Co-authored-by: Wojciech Mazur <wojciech.mazur95@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 396a781 - Browse repository at this point
Copy the full SHA 396a781View commit details
Commits on Jun 18, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 142264c - Browse repository at this point
Copy the full SHA 142264cView 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 fix-callback-timer...master