Closed cstjean closed 6 years ago
The no-no is on this line; we can't import read
because we want to define our own Feather.read(::String)
method.
Wow, that was an embarrassing screw-up on my part. I'll fix this by tonight.
Looks like one of the artifacts of my very early experimental work with this that survived my purges when it shouldn't have.
Kind of amazing that I haven't encountered this error myself yet.
No worries; we're being a bit funny anyway by defining our own Feather.read
method; I like it and prefer that the top-level API be Feather.read
, but it just means that all Base uses of read
in Feather have to be explicitly referenced Base.read
.
We'll want to not import write
either. And as a style note, I don't like doing these kind of import
statements at all; I prefer to explicitly annotate the actual method definition like Base.size(::MyType) = ...
. That way I don't have to remember to update/modify an import list and it makes it very clear at method definition site that a method is either extending a Base method or defining its own.
Yes, I agree the Base.func
syntax is much better, I've recently come around to this way of thinking about it.
I'll make all the changes tonight. Eventually I'll probably change Arrow.jl to that style as well.
Should be fixed now on master.
Assuming this is fixed. Please re-open if you are still experiencing an issue.
Any chance that Feather.jl could be tagged? I've been using master
for a month, and it's working great.
That's great to hear. I've also been using master
extensively since I rewrote it and indeed everything seems fine.
@quinnj indicated that there is missing DataStreams integration, but that's up to him as I'm not sure what remains to be done.
I have no objections to tagging now. I think that, at the very latest, we should tag very soon after the 0.7 release.
On 0.6, OSX
@ExpandingMan ?