From: "ko1 (Koichi Sasada)" <redmine@...>
Date: 2013-01-25T12:06:56+09:00
Subject: [ruby-core:51631] [ruby-trunk - Feature #7730] Top level variables aren't checked for assigned but unused behavior


Issue #7730 has been updated by ko1 (Koichi Sasada).

Category set to core
Assignee set to nobu (Nobuyoshi Nakada)
Target version set to next minor

Nobu, do you need matz's approval?

----------------------------------------
Feature #7730: Top level variables aren't checked for assigned but unused behavior
https://bugs.ruby-lang.org/issues/7730#change-35592

Author: agrimm (Andrew Grimm)
Status: Open
Priority: Normal
Assignee: nobu (Nobuyoshi Nakada)
Category: core
Target version: next minor


In the following code, variable a in the method gets a warning, but variable b in top level code doesn't get any warning

    def warning_method
      a = 2
    end

    b = 2
    warning_method

    $ ruby -w no_toplevel_warnings.rb 
    no_toplevel_warnings.rb:2: warning: assigned but unused variable - a

It is possible to detect that b is unused if the script is required from another script.

I'd like Ruby to be able to detect that b is an assigned but unused variable.


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