Repository navigation
Document that Loop.new raises RuntimeError when no backend is usable - #125
Merged
Merged
Conversation
PR socketry#119 made Loop.new raise RuntimeError instead of crashing when no selected backend is usable. The documentation did not mention it, or that $LIBEV_FLAGS can cause it unless :skip_environment is true. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Since #119,
Coolio::Loop.newraisesRuntimeErrorinstead of crashing when none of the selected backends is usable. The rdoc did not mention it, or that$LIBEV_FLAGScan override the backend selection and cause it unless:skip_environmentis true. This adds that to the rdoc ofinitialize.Types of Changes
Contribution
🤖 Generated with Claude Code