Note that this behavior was copied from Ruby, so maybe there's a reason to it. But if we change this, we should change Hash too and check other places too.

I'd rather revert suffixes in numbers. They are too noisy.

So someone came saying they depended on the to_s output format of array and suddenly we have to changer things? Why on earth aren't we just saying "don't depend on to_s/inspect on array".

I don't know, I can't decide this anymore. For me it's just noise.

Nevermind, let's fix to_s to use to_s. But please fix all of these:

• Array
• Hash
• Tuple
• Slice
• StaticArray
• Deque
• Set

I think that knowing the runtime type of something is a huge part of the inspect output. Inspect is largely used for debugging and knowing the type when debugging is hugely useful for reasoning about its behaviour.

@bew would you want to include the rest of the containers in this PR?

The failing spec shows a case that we are not analyzing.
["foo"].to_s should be ["foo"] (T.inspect) or [foo] (T.to_s).

Maybe it's wrong to assume that there is a human (non-programmer) readable form of the containers, hence the current behaviour could be ok.

@bcardiff yes, I can do that later today

Yup, that's a good reason why Array uses inspect. Plus, Array is really for programmers, not a general output that you should be sending down the wire.

I think there's nothing to do here: don't use Array#to_s nor Array#inspect if you don't want to get type info.

Ok, just understood your comment @bcardiff, that's a good point. Let's leave it that way then.