-
**Describe the bug**
The code means more than a thousand words:
```python
>>> p1 = cg.Point(1.2, 4, 3)
>>> p1
Point(x=1.2, y=4.0, z=3.0)
>>> p1 * 0.5
Point(x=0.6, …
-
From interpreting the stack trace, this looks like the same underlying issue as https://github.com/servo/servo/issues/32454. When the parser is synchronously parsing and a GC occurs, we attempt to mut…
-
I tried this code:
```rust
static mut WRAP_COUNTER: Option = None;
/// This function is safe and should never crash. Counter starts at 0.
#[kani::modifies(std::ptr::addr_of!(WRAP_COUNTER))]
#[k…
-
The requirements for a mutable reference to the cache in combination with returning a reference is problematic. Change this to a form of interior mutability.
-
It would useful to have a function like
```hs
mutableArrayFromListN :: PrimMonad m => Int -> [a] -> m (MutableArray (PrimState m) a)
```
given that there already exists
```hs
arrayFromList…
-
The simulation currently has multiple ways to manage the material of a solid or fluid. It is managed by a named enumeration plus a Material instance. In some, but not all cases, there is a 2-way bindi…
-
### Describe the bug
When pushing the latest release to Play Console, it provided warnings about:
```
Apps targeting Android 12 or later must specify the mutability of PendingIntents with either …
-
Thanks for the great project.
I am using rustc 1.77.2, when I run `cargo test`, it warnning:
```txt
warning: creating a mutable reference to mutable static is discouraged
--> src/trace.rs:104…
-
### Summary
```rust
#![deny(clippy::borrow_interior_mutable_const)]
use std::cell::UnsafeCell;
const ATOMIC_TUPLE: (Vec, u8) = (Vec::new(), 42);
fn main() {
let _x = &ATOMIC_TUPLE.0;…
-
Starting with Rust version 1.77 (released a few days ago), there is a new compiler warning related to "mutable reference to mutable static".
Given a simple Faust DSP like
```faust
import("stdf…