hotpatch icon indicating copy to clipboard operation
hotpatch copied to clipboard

Changing function definitions at runtime in Rust

Results 5 hotpatch issues
Sort by recently updated
recently updated
newest added

Currently, the only unsafe portion of this crate is that trying to patch a parent function (without the unsafe `force`) causes a deadlock. Using the `backtrace` crate it may be...

I have no idea if this crate works already with webassembly or not, but just in case, it might be a good idea to make it work on webassembly.

I intend to work on implementing methods when I next have time. An implementation draft can be found in #7. I'm currently concerned with the need to import traits to...

help wanted

As mentioned in [this](https://reddit.com/r/rust/comments/kfwtd9/hotpatch_safely_changing_function_definitions_at/ggdf4s4?context=3) reddit comment, if a patch implementation from an external library has `unsafe` code then `patchable` functions should require `unsafe`. As this crate already exports some information...

enhancement

Hello, I’m exploring hot-patching in Rust and have two main questions: - It seems so far most work (including this crate) is focused on replacing libraries / shared-objects at runtime,...