< :前の番号
^ :番号順リスト
> :次の番号
P :前の記事
N :次の記事(スレッド移動)
|<:スレッドの先頭
>|:次のスレッド
^ :返事先
_:自分への返事
>:同じ返事先を持つ記事(前)
<:同じ返事先を持つ記事(後)
---:分割してスレッド表示、再表示
| :分割して(縦)スレッド表示、再表示
~ :スレッドのフレーム消去
.:インデックス
..:インデックスのインデックス
chopraanmol1 / gmail.com wrote:
> https://bugs.ruby-lang.org/issues/15251
> I'm not sure if current behavior is expected one or a bug. So fell free to
> change tracker type.
current behavior is intentional because of a regression case:
https://bugs.ruby-lang.org/issues/9188
> Currently Hash aset checks if non-tainted string exists in
> fstring table or not, if it does not then ruby duplicates
> string and freeze it. This works well for string_literal
> because they are already registered in fstring table during
> compilation, but it doesn't work for non-string literal.
Right, I prefer we always dedupe since more programs will
benefit. We can take a small regression for programs that write
uncommon/random keys to hashes.
Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>