ruby.git/test/ruby/test_object.rb, branch v3_2_11

Use rb_inspect instead of +PRIsVALUE for Object.inspect

2022-12-09T13:11:00+00:00

In order to preserve the values when TrueClass, FalseClass or NilClass
are stored in ivars

Freeze singleton class, not its origin

2022-12-08T20:58:26+00:00

Previously, when we froze an object, we froze
`RCLASS_ORIGIN(object.singleton_class)`, which didn't freeze
`object.singleton_class` when it has some prepended modules.

Origin iclass are internal objects and users can't interact with
them through Kernel#freeze?, Kernel#freeze, or any mutation method
that checks the frozen status. So we shouldn't touch the origin
iclasses when the frozen status should be visible.

[Bug #19169]

Revert "Revert "This commit implements the Object Shapes technique in CRuby.""

2022-10-11T15:40:56+00:00

This reverts commit 9a6803c90b817f70389cae10d60b50ad752da48f.

Revert "This commit implements the Object Shapes technique in CRuby."

2022-09-30T23:01:50+00:00

This reverts commit 68bc9e2e97d12f80df0d113e284864e225f771c2.

Fix frozen object inspect

2022-09-30T20:57:59+00:00

In the rails/rails CI build for Ruby master we found that some tests
were failing due to inspect on a frozen object being incorrect.

An object's instance variable count was incorrect when frozen causing
the object's inspect to not splat out the object.

This fixes the issue and adds a test for inspecting frozen objects.

Co-Authored-By: Jemma Issroff 
Co-Authored-By: Aaron Patterson

[WIP] add error_squiggle gem

2021-06-29T14:45:49+00:00

```
$ ./local/bin/ruby -e '1.time {}'
-e:1:in `': undefined method `time' for 1:Integer (NoMethodError)

1.time {}
 ^^^^^
Did you mean?  times
```

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

test/ruby: Check warning messages at a finer granularity

2020-12-17T11:06:18+00:00

Instead of suppressing all warnings wholly in each test scripts by
setting `$VERBOSE` to `nil` in `setup` methods.

Disable deprecation warning by the default [Feature #16345]

2020-09-25T00:50:33+00:00

And `-w` option turns it on.

Support obj.clone(freeze: true) for freezing clone

2020-03-22T16:30:07+00:00

This freezes the clone even if the receiver is not frozen.  It
is only for consistency with freeze: false not freezing the clone
even if the receiver is frozen.

Because Object#clone is now partially implemented in Ruby and
not fully implemented in C, freeze: nil must be supported to
provide the default behavior of only freezing the clone if the
receiver is frozen.

This requires modifying delegate and set, to set freeze: nil
instead of freeze: true as the keyword parameter for
initialize_clone.  Those are the two libraries in stdlib that
override initialize_clone.

Implements [Feature #16175]

Suppress some warnings

2020-01-06T16:33:30+00:00

```
.../ruby/test/ruby/test_keyword.rb:3509: warning: assigned but unused variable - bug8993
.../ruby/test/ruby/test_object.rb:83: warning: assigned but unused variable - f
.../ruby/test/ruby/test_object.rb:95: warning: method redefined; discarding old initialize_clone
.../ruby/test/ruby/test_object.rb:84: warning: previous definition of initialize_clone was here
```