Bjørn Erik Pedersen

>Because this is how Go's os package behaves. Go does not have a memory mapped filesystem in its Stdlib. >This is only a breaking change for code that relied on...

>I think yes because otherwise afero couldn't be used to replace the os filesystem in unit tests without producing different results. I would say that writing unit tests against the...

Are any of those issues fixed by this patch?

>I would say that writing unit tests against the OS root filesystem would be a rare thing. The above sentence does not make much sense, I meant: "unit tests against...

>Does the example in my above comment answer your question? Not really. Having client code interact directly with the root of the OS filesystem is most likely not what you...

What is `reflect.Values` and what is its purpose in that function? What's wrong with just doing `v := reflect.ValueOf(i)`?

The "is wrong" statement is a little bombastic -- but the current behaviour is certainly a little undocumented. But it's certainly in line with the corresponding documentation in Go's stdlib....

@liuaiyuan this isn't my library and I did not implement these, and I would probably also prefer that they behaved the way you describe, but that would probably be too...

What do you mean by "friendlier result"?

I wish we could add this, but the introduction of comma, while it feels natural, would be breaking. >{"a,b", []string{"a", "b"}, false}, Someone may depend the above test case returning...