en_migi
Se unió el 17 noviembre 2023
Mensajes en el foro
-
Respondió en Does Rust 1.85 still let me call a variable gen?
それは私です。コーヒーをいれます。And yes, I forgot to change the use on my first try. Let me have my coffee while it's still an identifier in both editions.
-
Respondió en Does Rust 1.85 still let me call a variable gen?
let r gen = 3; , Then println!("{}", r gen); produces 3 with either edition. That does the little program. Really it's the day to ask why we named seventeen things gen.
-
Respondió en Does Rust 1.85 still let me call a variable gen?
Same 1.85.0. Minimal main with that binding and a print of it: edition 2021 accepts gen. Edition 2024 rejects it as a reserved keyword. No change to what three means, it's the spelling of the local n…
-
Inició Does Rust 1.85 still let me call a variable gen?
Rust 1.85, including the 2024 edition. My little crate has let gen = 3; . Old manifest still says 2021. It did not promptly burst into flames upon hearing today's good news. Whose editor hand-edited…
-
Respondió en What did I put inside Go 1.24's b.Loop()?
So the claimed speedup compared different work. You might still care about the time from a cold start till the first match. Could you keep that as a second benchmark with opening INSIDE, instead of d…
-
Respondió en A reversing student can see two MUL instructions in my calculator and charges me for both
Is the loop body entered once per element, without early exits? Two sites, four executions with your three-element input. One execution if the list is empty and you still do the post-loop multiply.
-
Respondió en My tiny disassembler can list both paths. My tiny CPU takes one and goes for lunch.
Starting at 0, where's any transition to 3? Seeing a card, being able to get to it and having gone there on this run are three separate little pleasures.
-
Respondió en Postgres: current transaction is aborted. The next SELECT is an innocent bystander.
The first error is the duplicate key, SQLSTATE 23505. The later one is 25P02, the transaction's failed state. No amount of simplifying that SELECT will make the original transaction healthy.
-
Respondió en They've offered to put a window on my field-note reader. Which of you called my mother?
How does that survive editing a note? If I correct "gull" to "gate" and its identifier changes, the thing in your draft that says after-id 4 will be sending postcards to the recently deceased.
-
Respondió en Le di una página más a WebAssembly y mi Uint8Array se ha quedado sin ninguna
grow(1) Returns the old size in pages, so 1 here. The old ArrayBuffer is detached for that non-shared memory. Read m.buffer again, then create the new view. Does the 42 still live at index zero?
-
Respondió en Rust 1.83 lets my const fn borrow the counter mutably. The finished constant doesn't want it back.
Then it's nine. That was my actual little question: the computation can depend on which number I start with, and there's still no mutable thing left inside the result. I withdraw my patent on the dig…
-
Respondió en Rust 1.83 lets my const fn borrow the counter mutably. The finished constant doesn't want it back.
The release explicitly shows that case rejected: the final value of a constant can't be that reference to mutable memory. Fine with borrowing my pencil, disinclined to ship the pencil inside the seve…
-
Respondió en Rust 1.83 lets my const fn borrow the counter mutably. The finished constant doesn't want it back.
const fn two_more(n: &mut u8) { n += 2; } And const COUNT: u8 = { let mut n = 5; two_more(&mut n); n }; . That's 7. The temporary reference did its work before the constant finished.
-
Inició Rust 1.83 lets my const fn borrow the counter mutably. The finished constant doesn't want it back.
Rust 1.83 lets our compile-time counter borrow mutably for a moment. I feed a local value to a const fn that adds two. The finished number comes out looking boringly immutable. Where did my glorious…
-
Respondió en he enviado ocho bytes de dignidad desde una función que juraba conocer doce enteros
The array parameter written that way is adjusted to a pointer parameter. The call doesn't carry a hidden count of twelve. On your machine the pointer happens to be eight bytes and the twelve-element…
-
Respondió en mi función de unir intervalos funciona estupendamente si ya le doy los intervalos unidos
My favourite boring question about your fuzzer: if it finds another case after three thousand little noises, can I get the actual list of endpoints? I am not listening to three thousand clips of your…
-
Respondió en My own executable contains the word APRICOT. A roomful of people insist it must print APRICOT.
Which bloody build, @rtb_402? Could an optimiser throw the unused string away? I've sat through enough shit about binaries where the eternal law turns out to be "by the way, that was my debug build".
-
Respondió en Python: RuntimeError: dictionary changed size during iteration. El eliminado sigo siendo yo
A new dictionary containing only the players who attended would also work if you're free to replace the object. If the scoreboard still holds a reference to THIS dictionary, changing the original and…
-
Respondió en Swift 6 arrived. My two modules are no longer on speaking terms about one mutable value
One caption job in Spanish, another in English, both rendering their own names now. Old way happened to work when the second job started AFTER the first ended. New test starts them together and check…
-
Respondió en Swift 6 arrived. My two modules are no longer on speaking terms about one mutable value
@TessellateLater The strings for our title card never change once loaded. Made those an immutable value local to the caption job. The live counter DOES change and belongs to that job, not every rende…
-
Respondió en Swift 6 arrived. My two modules are no longer on speaking terms about one mutable value
Captions only. Its shared mutable caption cache now gets a concurrency-safety error in the new mode. Other module still uses five. My colleague's first idea was to make the diagnostic less audible.
-
Inició Swift 6 arrived. My two modules are no longer on speaking terms about one mutable value
Swift 6 arrived. Our tiny demo has a captions module and a renderer. The school of whatever-compiles says we upgraded the compiler so we've already moved both modules to the new language mode. That's…
-
Respondió en Rust E0382: borrow of moved value. ¿Qué se ha llevado el bucle?
The loop asks for an iterator over nombres by value. The Vec is consumed and yields owned Strings. Later you're asking the old binding for its length. Do you need the loop to OWN a name in order to p…
-
Respondió en C linker: multiple definition of counter. There is ONE header and I will die on this hill
My favourite offer was "send me the executable and I'll look". Mate if I ever produce an executable I'm taking it out for a drink.
-
Respondió en C linker: multiple definition of counter. There is ONE header and I will die on this hill
Then each translation unit gets its own counter. bump can increment its own copy all evening while show is still staring at zero. One extern declaration and one definition: bump once, show prints 1.
-
Respondió en C linker: multiple definition of counter. There is ONE header and I will die on this hill
Two .o files. Both compiled separately without a peep. Complaint only when the two get married. Your tone is shit but I suspect you've just told me the answer.
-
Inició C linker: multiple definition of counter. There is ONE header and I will die on this hill
multiple definition of 'counter' From the linker. My header contains int counter = 0; and has an include guard. bump.c includes it. show.c includes it. There is one physical header. I'd like to know…
-
Respondió en Rust 1.80: dos dibujos me piden la misma tabla de senos. Se ha presentado un solo cocinero
Yes. Pure one-off initialisation plus later reads is easy to reason about. If the actual application wants a changing table, it needs to say how those changes are coordinated. Different question, dif…
-
Respondió en Rust 1.80: dos dibujos me piden la misma tabla de senos. Se ha presentado un solo cocinero
Use the same static for both drawings. A counter inside the initialisation function answers a narrower and much more useful question than "was frame one slow". Two different lazy values are allowed t…
-
Respondió en ¿Para qué quiero recursividad si ya tengo un for que va de lujo?
Yes. Your function calls remember which child comes next. A loop can keep its own pile of pieces to visit and do the same work. Four leaves either way; one slightly heavier piece of cardboard.