From: naruse@... Date: 2018-01-03T18:15:22+00:00 Subject: [ruby-core:84618] [Ruby trunk Bug#14247] Thread#fetch raise KeyError without key and receiver Issue #14247 has been updated by naruse (Yui NARUSE). Backport changed from 2.3: DONTNEED, 2.4: DONTNEED, 2.5: REQUIRED to 2.3: DONTNEED, 2.4: DONTNEED, 2.5: DONE ruby_2_5 r61583 merged revision(s) 61507. ---------------------------------------- Bug #14247: Thread#fetch raise KeyError without key and receiver https://bugs.ruby-lang.org/issues/14247#change-69163 * Author: znz (Kazuhiro NISHIYAMA) * Status: Closed * Priority: Normal * Assignee: znz (Kazuhiro NISHIYAMA) * Target version: * ruby -v: ruby 2.6.0dev (2017-12-27 trunk 61494) [x86_64-linux] * Backport: 2.3: DONTNEED, 2.4: DONTNEED, 2.5: DONE ---------------------------------------- I found this by message without `Did you mean?`. expected: ``` % ruby -e 'th=Thread.current;th[:foo]=1;th.fetch(:fooo)' Traceback (most recent call last): 1: from -e:1:in `
' -e:1:in `fetch': key not found: "fooo" (KeyError) Did you mean? :foo ``` actual: ``` % ruby -e 'th=Thread.current;th[:foo]=1;th.fetch(:fooo)' Traceback (most recent call last): 1: from -e:1:in `
' -e:1:in `fetch': key not found: fooo (KeyError) ``` ---Files-------------------------------- Thread-KeyError.diff (870 Bytes) 0001-Fix-KeyError-key-receiver-of-Thread-fetch.patch (1.22 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: