magick-rust VS rust

Hi, I want to make a small image server that can return an image resized to arbitrary dimensions from a source. I could just use something like this: https://github.com/nlfiedler/magick-rust (ImageMagick bindings) but I'm curious if there is a way to do it with pure rust. Thanks!

https://github.com/nlfiedler/magick-rust#dependencies

If you look at the history of the author's own sorting implementation (ipnsort), it started as an attempt to port fluxsort to Rust:

https://github.com/Voultapher/Presentations/blob/master/rust...

It starts there, eventually the author abandons the linked PR because of a better approach found with ipnsort:

https://github.com/rust-lang/rust/pull/100856#issuecomment-1...

And if procedural macros can have state, then you don't need RFC for `distributed_slice`, there is old bug about this https://github.com/rust-lang/rust/issues/44034

Long before my PR, there was issue #46477, "Instantiate fewer copies of a closure inside a generic function." The Polymorphization WG was started up from that, but I don't know their current status.

The second is the use of fn check. This is much more esoteric and is primarily about controlling compile times and generated code size, due to shortcomings in the current monomorphization implementation. Basically, when you use a lambda (as would be expected), you end up with a lot of necessary generic parameters that result in a lot of extra versions of that function body being compiled. fn check, being an item, doesn't retain any generic context from its surrounding scope, so it only has to be compiled once for each it encounters. The relevant PR is here and it links out to plenty of discussions describing the problem and why it was solved this way.

The major one on PC are macOS, Windows and Linux. On Windows I suppose rust std lib already don't use libc for the most cases: https://github.com/rust-lang/rust/issues/20861 , Linux has stable syscall abi. So only macOS require to use libc.

IMO the biggest problem is that Rust is pretty lacking in the ability to dynamic link to code (which isn't a feature of OOP in general! It just so happen that many OOP languages also have this feature), which translates in a poor ability to write plugin systems and hot-reload code. This is not an intrinsic limitation of Rust the language though, just the tooling around it, and there is work in progress to mitigate the issue.

I came across this issue in Rust recently: https://github.com/rust-lang/rust/issues/57893. I thought it was interesting since it lets you easily write transmute in safe Rust: https://zyedidia.github.io/blog/posts/5-safe-transmute/.