Hm, I want to make things convenient for the developer, but I don't think that extends to not requiring them to know the difference between a rune and a string.  I think any real use case would involve a constant expression where the fix is as simple as changing single quotes to double quotes, no?  

Another counter argument is that, unless I'm mistaken, this would then be the case:

```go
53 == "5"
50 != "50" 
```

which seems weird.. 

Anyway, I there is definitely a gray area of how much conversion we should do.  Here is the scale as I see it:

1. Equivalent value and type (most conservative)
1. Equivalent value but different type size (int32 vs int64)  (initial request)
2. Equivalent value but requires type conversion ([]byte to string)
4. Different concrete value, but identical conceptual value ("52" vs 52, rune('5') vs "5", []int{5} vs 5)

I was ok with []byte to string since that is a very common conversion and they really are the same underlying thing.  But I see a line before that last step which I am not comfortable to pass right now.    Sorry!