Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Start an idea of what an "in memory" requirement would look like #278

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Start an idea of what an "in memory" requirement would look like #278

wants to merge 1 commit into from
+26 −1

Commits on Mar 12, 2022

  1. Start an idea of what an "in memory" requirement would look like 

    This has been requested/discussed a number of times; here's one idea of
what this could look like. Basically the same as `Tables.rows`, but
`Tables.indexablerows` would require an "indexable" object of rows to be
returned instead of just an iterator. Indexable is a little vague; to be
most useful, we should probably require the return object to be
`AbstractVector` since we get lots of fancy indexing/useful behavior
that way. The bare minimum indexing interface is just `getindex`,
`firstindex`, and `lastindex`, but it seems like people would then just
be wanting to do `x[[i, j, k]]` like operations and have to implement
their own. So I'm inclined to make the requirement that you have to
return an `AbstractVector` of rows.
    @quinnj
    quinnj committed Mar 12, 2022
    Configuration menu
    Copy the full SHA
    6cd1f50 View commit details
    Browse the repository at this point in the history