# IO#set\_encoding without int\_enc doesn't keep current internal encoding

**URL:** <https://www.ruby-forum.com/t/io-set-encoding-without-int-enc-doesnt-keep-current-internal-encoding/234840>\
**Category:** Development\
**Created:** [October 22, 2014, 7:42pm UTC](https://www.ruby-forum.com/t/io-set-encoding-without-int-enc-doesnt-keep-current-internal-encoding/234840 "2014-10-22T19:42:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\
**Post date:** [October 22, 2014, 7:42pm UTC](https://www.ruby-forum.com/t/io-set-encoding-without-int-enc-doesnt-keep-current-internal-encoding/234840/1 "2014-10-22T19:42:55Z")

</div>

Issue #10417 has been updated by Yui NARUSE.

Target version changed from current: 2.2.0 to Next Major

fptr.encs.enc と fptr.encs.enc2 って不可分なものな気がするのと、  
set\_encoding というそれまでの前提が覆ってる状況で前の状態を尊重する理由をあんまり感じないので、  
現在の値を保持するべきだとはあまり思いません。

そもそも set\_encoding(ext\_enc, int\_enc, opts) の引数たちと内部の状態に若干解離があるとか、  
optsは吹っ飛ばさざるを得ないので、int\_encも飛ばしていいんじゃないとか、  
そもそもset\_encoding()って位置から設定し直すメソッドな雰囲気を感じている、とか。

* * *

Bug #10417: IO#set\_encoding without int\_enc doesn’t keep current  
internal encoding

> **[Bug #10417: IO#set\_encoding without int\_enc doesn't keep current internal...](https://bugs.ruby-lang.org/issues/10417#change-49589)**
>
> Redmine

- Author: Usaku NAKAMURA
- Status: Open
- Priority: Normal
- Assignee:
- Category: core
- Target version: Next Major
- ruby -v: -
- Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN