-54
submitted 6 months ago* (last edited 6 months ago) by Aatube@kbin.melroy.org to c/rust@programming.dev

Not to throw shade, just wishing that somebody here can understand. Whenever an input is reasonably long, an analyzing function will crash, and this PR aims to fix that with a mechanism that contradicts the maintainer's understanding while a similar C implementation does not need this fix. ~~Clearly, the maintainer has not heard a certain programming mantra...~~

you are viewing a single comment's thread
view the rest of the comments
[-] tyler@programming.dev 4 points 6 months ago

Looks to me like a reasonable conversation is happening trying to find the underlying issue. Where is the PR being held up?

[-] Aatube@kbin.melroy.org -2 points 6 months ago* (last edited 6 months ago)

Since I posted it, the conversation has moved forward. Before that it was just two people being justifiably confused.

[-] Maddier1993@programming.dev 4 points 6 months ago

You must understand that maintainers need to worry about supply chain attacks ever since the xz debacle. So I suggest you wait.

[-] Aatube@kbin.melroy.org 1 points 6 months ago

Thanks. All I wanted was to have someone answer with what's actually going on, and thanks to Giooschi below that has happened, and there indeed isn't anything to do at this point. I've tried to edit the post but couldn't find a proper wording.

this post was submitted on 18 Apr 2024
-54 points (9.1% liked)

Rust

5981 readers
29 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS