Code Monkey home page Code Monkey logo

Comments (5)

Majored avatar Majored commented on July 17, 2024 2

I've had a bit of time to play around and I quite like @NobodyXu's suggestion.

What I've come up with is a type-driven approach in order to have compile-time guarantees about what methods can be called, rather than just having read_to_*_checked error or panic if it doesn't have an associated entry.

Readers now implement two entry reader methods:

pub async fn reader_without_entry(&mut self, index: usize) -> Result<ZipEntryReader<'_, R, WithoutEntry>> {

pub async fn reader_with_entry(&mut self, index: usize) -> Result<ZipEntryReader<'_, R, WithEntry<'_>>> {

This still needs a bit of polish but the documentation page would essentially look like this: https://imgur.com/a/HRQkGvr
Where the read_to_*_checked() methods are only defined on the WithEntry variant and no longer require it as a parameter.

I'm happy to settle on this unless anyone else has any other suggestions.

from rs-async-zip.

Majored avatar Majored commented on July 17, 2024 1

I've just pushed V0.0.15 which has the above changes - I'll go ahead and close this as a result. 👍

from rs-async-zip.

Majored avatar Majored commented on July 17, 2024

Yep, this wasn't something I ran into until after I had already switched over the API so didn't realise the implications at the time. That's why, unfortunately, the README example currently clones the ZipEntry to make it at least somewhat usable.

Whilst I wasn't a big fan of the old API (where a ZipEntryReader holds a reference to the ZipEntry itself), it worked well since there was a disjoint/split borrow on the ZipFileReader's fields.

Will hopefully tackle switching it back soon but feel free to do so if you happen to have the time.

from rs-async-zip.

NobodyXu avatar NobodyXu commented on July 17, 2024

Whilst I wasn't a big fan of the old API (where a ZipEntryReader holds a reference to the ZipEntry itself), it worked well since there was a disjoint/split borrow on the ZipFileReader's fields.

I have another idea of fixing this, by adding a new API to ZipFileReader:

pub fn entry_and_reader(&mut self) -> (&ZipEntry, &mut ZipEntryReader<...>);

from rs-async-zip.

moutikabdessabour avatar moutikabdessabour commented on July 17, 2024

Please make this clear in the documentation. something as simple as creating an iterator over the entries and checking if the filename is in a list and then decompressing doesn't work because of the issue highlighted in the first comment.

from rs-async-zip.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.