When should I use references for Vec, Box, slices, etc.?Īlso, I'm lost with regards to "idiomatic" Rust. For instance, how do I pass a fixed size (at compile time) array to a function, and get a new fixed size array back? I don't want Vec because it's too dynamic, and I'm clueless as to how to use Box.
I'm not sure when a function call is copying memory unnecessarily and when it isn't. Greater performance than the JavaScript versionĬompile to any target on any platform (including embedded and WASM - I believe no_std helps with this?)Īllow for multithreaded processing on supported targets, and fallback to single thread on unsupported targets such as WASMĪs I have very little experience with low-level languages, borrowing and ownership have been confusing to me.
I'm very new to Rust, so I really have no idea what I'm doing. I would hope a port to Rust would improve performance much beyond standard Rust implementations. I compared libflate and flate2 to my NPM package and found they all actually performed quite similarly (compression speed of fflate 5% slower than flate2 and 10% faster than libflate) running libflate's benchmark. I've been interested in porting this to a GC-less, compiled language to see how far I can take my algorithmic improvements. I recently authored an NPM data compression package fflate with a heavy emphasis on performance and small size.
0 kommentar(er)
