Project

General

Profile

Feature #16752

:private param for const_set

Added by bughit (bug hit) 8 months ago. Updated 8 months ago.

Status:
Open
Priority:
Normal
Assignee:
-
Target version:
-
[ruby-core:97680]

Description

Defining a private constant should not require two method calls.

You want to encourage private declarations because they communicate intent better and are easier to refactor, two statements discourage it.

Ideally there should be compact syntax for direct private declarations, but that's probably a difficult change.

But const_set :FOO, 1, private: true or const_set :FOO, 1, :private should be trivial


Related issues

Related to Ruby master - Feature #17171: Why is the visibility of constants not affected by `private`?RejectedActions

Also available in: Atom PDF