From: mail@...
Date: 2015-08-22T07:04:21+00:00
Subject: [ruby-core:70543] [Ruby trunk - Feature #11252] Integrated "did_you_mean" gem to ruby-core

Issue #11252 has been updated by Yuki Nishijima.


We've discussed this at the Ruby developers meeting on Thursday and made several decisions(but still subject to change).

  * We are not going to rename the gem (we'll just use `did_you_mean`)
  * It'll be a bundled gem (Yuki will be responsible for releasing a version that works on Ruby 2.3 without C extensions)
  * There should be a way of disabling this feature entirely (`--disable-gem did_you_mean` or `--disable-gemname`)
  * There should be a method on `NameError` that returns a qualified name:

    ```ruby
    class User; end

    error = begin
      User::DoesntExist
    rescue NameError => e
      e
    end

    error.name           # => :Exist
    error.qualified_name # => :"User::DoesntExist"
    ```

The last 2 features can be separate features. That said, since the last one is a blocker, it would be great if this could be done before actually having did_you_mean bundled.

----------------------------------------
Feature #11252: Integrated "did_you_mean" gem to ruby-core
https://bugs.ruby-lang.org/issues/11252#change-53951

* Author: Hiroshi SHIBATA
* Status: Open
* Priority: Normal
* Assignee: Hiroshi SHIBATA
----------------------------------------
Matz hope to integrate "did_you_mean" gem to Ruby 2.3

We need to solve to following issues.

 * integrate [interception](https://github.com/ConradIrwin/interception/) gem
 * naming(better name for did_you_mean)
 * bundled policy(standard library? bundled gem?)





-- 
https://bugs.ruby-lang.org/