NHDaly opened a new issue #310:
URL: https://github.com/apache/arrow-julia/issues/310
I was surprised by this when I was writing a unit test that a function
returned the expected structure.
For example:
```julia
julia> t = let io = IOBuffer(); Arrow.write(io, (v1=collect(1:10),));
seekstart(io); Arrow.Table(io) end
Arrow.Table with 10 rows, 1 columns, and schema:
:v1 Int64
julia> t2 = let io = IOBuffer(); Arrow.write(io, (v1=collect(1:10),));
seekstart(io); Arrow.Table(io) end
Arrow.Table with 10 rows, 1 columns, and schema:
:v1 Int64
julia> t == t2
false
```
Is the reason for this because it would be too expensive? I think users
generally understand that `==` on large collections is expensive and should
probably be avoided. Or is it because we don't want to have to implement an
expensive `hash()` function, and we'd have to do that if we implement `==`?
Thanks! :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
