cyrgani

This error can be caused just by `RUSTFLAGS="-Clinker-plugin-lto -Zsanitizer=cfi" cargo b` on an empty crate with the `compiler_builtins = "=0.1.160"` dependency. It is only caused by `compiler_builtins v0.1.157` and above,...

seems to require just `rustc -Clinker-plugin-lto -Zsanitizer=cfi src/main.rs` ```rust #![no_builtins] fn main() {} ```

The problem is that this line `let t = thickness / 2.;` is just wrong. If you remove it, the rectangle with width 1 is drawn as expected:  It...

#758 fixes this issue.

Given that `&raw` syntax might get stabilized soon by #127679, suggesting the correct `&raw mut` syntax would become a more feasible option.

@rustbot label: -D-invalid-suggestion

It would, but we cannot change that until a future release of macroquad 0.5, since it would currently break all usages of this function. Some more explanation can be found...

The error comes from this `Drop` implementation: ```rust impl Drop for GlPipelineGuarded { fn drop(&mut self) { get_context().gl.delete_pipeline(self.0); } } ``` The mutable static `CONTEXT` contains a `Option` object. `get_context`...

The error changed with the release of the latest miniquad version: it panics now instead of causing visible UB: ``` thread 'coroutine_execution_order' panicked at /home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/miniquad-0.4.5/src/lib.rs:90:29: NATIVE_DISPLAY already set ```

This needs to be fixed within miniquad as even this minimized example of two macroquad tests without content panics: ```rust pub mod test { pub static mut MUTEX: Option =...