exif-rs VS rust-analyzer

I dont want the files to waste a lot of space so i decided to resize them. For that i used the resize method from the "image" crate. Everything works fine, until i start to upload images above 5mb. Then the resize method starts to rotate the images. I think i narrowed it down to the resize function deleting any existing exif data inside the image file. That way the orientation flag is removed and the image is in its default position. I already tried to fix this, by saving the exif data before resizing and then rewriting it to the image file. The only library that i could find that supports writing (at least for png and jpeg) was this one: kamadax-exif. The problem is, that when i write the exif data (all the previous data or just the orientation data) the file gets corrupted. Now to my question: Can someone recommend a library that can resize images, that preserves the aspect ratio and does not delete the exif data? if not, does someone have an idea on how to resize the images differently? Or maybe there exists another exif data crate that i can use? I hope this question is understandable, thanks in advance :)

I absolutely loved all the crates available that made my life very simple in many cases. I used (among others) the slint ui framework, kamadak-exif, img_hash, fast_image_resize and rawloader.

go build 3.62s user 0.76s system 171% cpu 2.545 total

I was looking forward to parallel front-end[4], but I have not seen any improvement for these small changes.

[1]: https://github.com/rust-lang/rust-analyzer

For example, intelephense can show diagnostics in real time, there is no need to save the file to get new diagnostics. But rust-analyzer, the language server for rust, can only update diagnostics after saving the file.

6. Rust Analyzer

Agree this is not a problem. rust-analyzer also includes a boatload of custom extensions. Here's how "query type of selected expression" works, for example:

https://github.com/rust-lang/rust-analyzer/blob/master/docs/...

For example: https://github.com/rust-lang/rust-analyzer/blob/master/docs/...

> If you create an LSP, it will work best in VS Code.

Any editor can work just as well as (or even better than) VS Code.

I am not a Rust dev. It surely looks great.

However, from what I understand it seems to supply just a parser separate from the Rust compiler (https://github.com/rust-lang/rust-analyzer/tree/master/crate...) trying to keep up with Rust‘s development. So, in principle, it could have been just another treesitter parser plugin, too.

So, again, the LSP framework does not directly provide any magical benefit over a static parsing framework. All the semantic analysis capabilities stem from a good parser.

You may file issue at github rust-analyzer

I've contributed to rust-analyzer and nushell and had a great experience in both! Tons of open issues with a huge range of difficulties, and the maintainers are really helpful in providing hints to get started.

For something more concrete you can try and ask around on their zulip or browse their issues.

More info here: https://rust-analyzer.github.io/ and here: https://rust-analyzer.github.io/manual.html#installation