refactor readers to use type parameters and not concrete vtables #2810

refactor readers to use type parameters and not concrete vtables

Usage Workflow file

16 warnings

The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

unresolved link to `ZipFile::enclosed_name`

unresolved link to `ZipFile::enclosed_name`

unresolved link to `crate::read::ZipFile::last_modified`

unresolved link to `BufWriter::flush`

unresolved link to `ZipFile::enclosed_name`

unresolved link to `Component::ParentDir`

unresolved link to `ZipFile::enclosed_name`

unresolved link to `Path`

unresolved link to `ZipFile::mangled_name`

`zip` (lib doc) generated 9 warnings