Closed
Conversation
Member
|
The plan is to support them, it's just low priority. |
Author
|
Jruby has it's own async Implementation. So anyone on JRuby already has primitives like Promises, Futures, and ThreadPoolExecutor, which don't require a fiber scheduler shim. People using these 2 engines mix Java and Ruby in the same codebase. |
Member
|
There are plans to unify them using virtual threads. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Remove JRuby and TruffleRuby from CI configuration, add required_ruby_engine restriction to gemspec, and simplify Ruby engine checks in scheduler.rb.
Async depends on gems that require C compilation (io-event), and Java engines already have their own async counterparts.