Skip to content

[DOC] Tweaks for StringIO#closed? #151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kou merged 1 commit into from
Oct 26, 2025
Merged

[DOC] Tweaks for StringIO#closed? #151

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions ext/stringio/stringio.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -614,8 +614,16 @@ strio_close_write(VALUE self)
* call-seq:
* closed? -> true or false
*
* Returns +true+ if +self+ is closed for both reading and writing,
* +false+ otherwise.
* Returns whether +self+ is closed for both reading and writing:
*
* strio = StringIO.new
* strio.closed? # => false # Open for reading and writing.
* strio.close_read
* strio.closed? # => false # Still open for writing.
* strio.close_write
* strio.closed? # => true # Now closed for both.
*
* Related: StringIO.closed_read?, StringIO.closed_write?.
*/
static VALUE
strio_closed(VALUE self)
Expand Down