Remove unsafe

[BillyDM]

I've been meaning to do this for a while, but I'm finally getting around to it.

I removed all uses of unsafe Rust, and there is no meaningful impact on performance. While the unsafe stuff was probably sound, I would much prefer to not have any unsafe if we can.

The main reason I used unsafe before was to avoid needing to zero out buffers before sending them to the decoder to fill. But I figured out I can get around this by just clearing the Vecs and using extend_from_slice() inside the decoder instead.

Although of course removing the unsafe is a breaking change, but I don't think there's anyone that was creating their own custom decoders and encoders anyway (if I'm wrong, please correct me). I think it's okay to just bump the version of creek to 1.2.0.

---

I also bumped the dependency versions since that was simple to do.

---

I also updated the demos to use the latest version of egui. I would have done this in a separate PR, but I wasn't able to get the old demos to run, and I wanted to use them to test if my changes still worked as expected.

[orottier]

Great to hear you were able to remove all unsafe without any real drawbacks. forbid_unsafe will definitely help getting trust of downstream users.

I only skimmed through the changes, but they look very reasonable to me. All demos work for me as well.

Changing a trait signature is a breaking change (read the final note over at https://doc.rust-lang.org/cargo/reference/semver.html#fn-unsafe-safe ) but it does seem a bit excessive indeed to increase major version. I'm no purist so v1.2 is fine with me.

[BillyDM]

Cool. I'll go ahead a merge this then.