Skip to content

Conversation

@BurdetteLamar
Copy link
Member

No description provided.

* call-seq:
* close_read -> nil
*
* Closes +self+ for reading; closed-write setting remains unchanged.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you remove the "closed-write setting remains unchanged" information?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's in the example code:

strio.closed_write? # => false

Could add comment if you like:

strio.closed_write? # => false  # Closed-write unchanged.

And same in #close_write.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an important information.

Could you keep this in the description part not the example part?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Restored.

Restore remark about closed-write.
@BurdetteLamar BurdetteLamar requested a review from kou October 26, 2025 17:26
@kou kou merged commit 11995db into ruby:master Oct 27, 2025
53 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants