feat: it's a bird, it's a plane, it's vortex-all!

[danking]

One crate to rule them all and in the darkness bind them.

[AdamGS]

Do we want this crate to re-export all the underlying dependencies?

[AdamGS]

We should probably also move a bunch of the docs in vortex-array here, but that can be a separate PR

[robert3005]

@danking as @AdamGS points out you have to reexport dependencies, otherwise none of the code referenced is accessible and it's just a dead dependency

[AdamGS]

and probably with some module structure, the same way arrow has arrow::schema and the arrow_schema crate

[danking]

I did this:

pub use vortex::*;
pub use {
    vortex_alp as alp, vortex_buffer as buffer, vortex_bytebool as bytebool,
    vortex_datetime_dtype as datetime_dtype, vortex_datetime_parts as datetime_parts,
    vortex_dict as dict, vortex_dtype as dtype, vortex_error as error, vortex_expr as expr,
    vortex_fastlanes as fastlanes, vortex_flatbuffers as flatbuffers, vortex_fsst as fsst,
    vortex_proto as proto, vortex_roaring as roaring, vortex_runend as runend,
    vortex_runend_bool as runend_bool, vortex_sampling_compressor as sampling_compressor,
    vortex_scalar as scalar, vortex_schema as schema, vortex_serde as serde,
    vortex_zigzag as zigzag,
};

[danking]

You can see what it looks like in bench-vortex and pyvortex now.

[danking]

I think we liked vortex as the module name and vortex-all as the package

[danking]

Auto merge disabled until #1124 merges.

[danking]

@robert3005 Do you have more mega PRs to land?

[robert3005]

None that you need to block on