[ruby-core:121564] [Ruby Feature#21219] `Object#inspect` accept a list of instance variables to display
From:
"byroot (Jean Boussier) via ruby-core" <ruby-core@...>
Date:
2025-04-07 18:44:16 UTC
List:
ruby-core #121564
Issue #21219 has been updated by byroot (Jean Boussier).
> could only symbols be used to simplify the syntax further?
Technically possible, but not ideal because of various implementation details (instance variables without a `@` prefix exist internally).
But regardless, it's also not good because then you can't use the values returned by `Object#instance_variables`.
----------------------------------------
Feature #21219: `Object#inspect` accept a list of instance variables to display
https://bugs.ruby-lang.org/issues/21219#change-112589
* Author: byroot (Jean Boussier)
* Status: Open
----------------------------------------
## Context
The default `Object#inspect` implementation is quite useful to have a generic representation of objects in error message and similar places.
However sometimes objects are referencing other objects with a very large `inspect` representation, making error message hard to understand.
In some other cases, some instance variables are holding secrets such as password or private keys, and the default inspect behavior can cause
these secrets to be leaked in logs among other places.
You can of course define your own `inspect` implementation for any object, but it's not as simple as it may seems because you need to handle circular references, otherwise you can end up with a `SystemStackError`.
Also, it's more minor, but since Ruby 2.7, you can no longer access an object's address, so you can't implement an `inspect` method that is consistent with `Object#inspect`
>>From my experience, user defined implementations of `#inspect` are very rare, and I think the above is in part responsible.
## Feature
I think it would be useful if the default `Object#inspect` implementation accepted a list of instance variables to display, so that you could very easily hide internal state, either because it's too verbose, or because it is secret:
```ruby
require 'logger'
logger = Logger.new(STDOUT)
class DatabaseConfig
def initialize(host, user, password)
@host = host
@user = user
@password = password
end
def inspect = super(instance_variables: [:@host, :@user])
end
env = {db_config: DatabaseConfig.new("localhost", "root", "hunter2")}
logger.info("something happened, env: #{env}")
```
```
INFO -- : something happened, env: {db_config: #<DatabaseConfig:0x00000001002b3a08 @host="localhost", @user="root">}
```
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/