https://github.com/sup/scala-vs-twitter-future

A brief comparison on behavior between Scala Futures and Twitter Futures on fatal exceptions
https://github.com/sup/scala-vs-twitter-future

Last synced: 8 days ago
JSON representation

A brief comparison on behavior between Scala Futures and Twitter Futures on fatal exceptions

• Host: GitHub
• URL: https://github.com/sup/scala-vs-twitter-future
• Owner: sup
• License: mit
• Created: 2024-02-24T21:22:45.000Z (11 months ago)
• Default Branch: main
• Last Pushed: 2024-02-24T21:48:51.000Z (11 months ago)
• Last Synced: 2024-11-09T04:38:01.233Z (2 months ago)
• Language: Scala
• Size: 20.5 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# scala-vs-twitter-future

A brief comparison on behavior between Scala Futures and Twitter Futures on fatal exceptions.

**Summary**

* Scala Future: Fatal exceptions will cause the future to hang. Any awaits on a composition of Scala Futures that involve a fatal exception like a `NonLocalReturnException` or `LinkageError` will never complete.

* Twitter Future: Fatal exceptions will cause the future to be completed exceptionally (Similar to a Java CompletableFuture).