Alexey Stukalov

OK, I've replaced the PR with the `findnext()` version. Both approaches should do more or less the same bit magic, so it's hard to say what would happen in the...

Yes, it would be nice to extract attributes. I'm just not sure how they should be returned to the user. Maybe 2 dictionaries: one for the objects, one for their...

Columns of a dataframe is a good example showing that it would be very hard if possible at all to recover all the attributes while converting R objects into Julia...

Thanks! I'll try to review it in the next few days.

I think tagging 1.0.0 is a good idea.

> Why not call that argument `makeunique` for consistency? `load()` can return different objects. I'm not sure it is as clear as in `DataFrame` ctor that `makeunique` refers to the...

I would be very much in favor of using the same corrected keyword as `DataFrame` ctor. Maybe something like `uniquenames`? Or `fixnames`, meaning that it will both make the name...

I cannot reproduce it. Also, AFAIK `Libz` is not used, `RData` uses `CodecZlib` instread. If you still have the issue, could you please show the full output of your Julia...

Thanks! Now I can reproduce it. The problem is that `.Rda` extension (case sensitive) is not registered in `FileIO` package, so `RData.load()` (which is just reexported `FileIO.load()`) tries to detect...

I also don't think `parse()` should return `missing` for invalid inputs. But somewhat more conservative thing would be to allow ```julia parse(Int, missing) = missing #= or =# parse(Union{Int, Missing},...