CheaterCodes

Fixed a critical error in https://github.com/QuiltMC/chasm/pull/108, which should fix your issue. A few things I noticed while investigating the code: - You can use ClassInfo.fromBytes() instead of the constructor -...

Chasm doesn't have a way to deal with Exceptions. I suppose we could allow throwing IOExceptions, but all we could do with that is wrap it in an Unchecked Exception...

> Similar reproduction as above, but just showing that it can easily be even more innocent than an explicit `drop` > > ```rust > let container = { > let...

Looking at this a bit closer, I can't think of any situation where this isn't - horribly unsound or - couldn't just use references internally. This struct should either -...

I also primarily agree that this should be *at least* two RFCs. I still have some comments regarding this though. I disagree with the idea that people want "lightweight clones"....

> ```rust > spawn(async move { > func1(use { x.clone() }).await; > func2(use { y.clone() }).await; > }); > ``` One problem I see with this is if you plan...