Glad it isn’t a yogurt commercial…

Perfect is really doing some heavy lifting. Sure shes better. I would have voted for her if i was an US-American. But shes still garbage. She kind of is controlled opposition. Making us look away from what would be actually good vs whats better than the worst option. It serves to legitimize their position in fear of the alternative. Thats not democracy. I am not saying that you should not vote, endorse or even accept the shitstain we get in the USA that is represented by Trump but running to the Democrats as the goal or seeing voting as the primary political action is a big blunder in my eyes. (again do vote).

I’d prefer there be less positions of power to stomp on women.

Don’t want to be associated with liberals nor MAGA.

The leftist who said “My goal is to make sure Grégoire loses” was defeated

Hmm. Even if I’m not sure I’d use the word “leftist” If you’re controlled opposition maybe don’t say it out loud lmao

Teaching liberals the word “tankie” was a mistake…

I mean… I want the war not to go well for the USA.

Keeping the working man in line. Or preserving the status quo.

For anyone interested, I did make a second version of the same logic. Even if i kind of had atomic operations in mind i did not know that i was thinking of atomic or what atomic was for that matter. So in a broad sense i assumed raw pointers were atomic. Also worth noting implementing a false Sync for &str seemed to be unnecessary to get it to run in the first example even if i got the impression during construction that it was. Just pretend in the first example “ExemptSyncStringSlice” is just &str if you want to compare them for some reason.

I don’t know the overhead of AtomicPtr compared to raw pointers and it is dependent on operating systems that can use an atomic load store (whatever that means.) But this version seems more “correct” at least.

use std::sync::atomic::{AtomicPtr, Ordering};
use std::time::Duration;


fn main()
{
	let pointer: AtomicPtr<&'static str> = AtomicPtr::new(&mut "Hello!");

	let mut value2: &'static str = "Hi!"; // Place outside scope due to lifetime.

	thread::scope(|scope|
	{
		scope.spawn
		(|| {
			for _ in 1..1000
			{
				unsafe { println!("String = {}",  *pointer.load(Ordering::Relaxed)); }
			}
		});

		scope.spawn
		(|| {
			sleep(Duration::from_millis(1));
			pointer.store(&mut value2, Ordering::Relaxed)
		});
	});
}

Thank you all who responded btw.

Well worst case to come with language design i could always learn assembly ;) Half joking but thank you very much for your answer. As for the example the only reason its rust is i figured it would be the easiest language to get the logic right even if i have more hours in C++ technically. Arrays seemed obvious enough that would break but i was unsure about things like pointers and integers. Just find the “lower” levels kinda fun ngl.

Hm. Good to know. As far as i know. rusts unsafe is kind of like sudo where more tools are granted to you with less checks and balances. Those checks being the borrow checker. So I think unsafe is more like saying “I don’t want the extra protection against bad memory use.” (Like say using memory you already freed). Now im not familiar with what makes a variable atomic or not. But assuming if a variable can be read or written with a single instruction. I’m interpereting that as making it safe?

Thank you for replying so quickly. Very interesting that it writes 64 bits at a time. (at least on the x86_64 platform i am on) So theres no tangible risk of a cpu processing a read and write instruction in parallel messing up the data that was read?

Knut Hamsun… That sounds very norwegi- …of course

Fuck!

I hate USA. I hate ISIS. I hate Turkey and the new Syrian Government too.

Not completely sure if you’re referring to ML’s or this meme but means and ends was published in 2023

This is why i find rmdir useful.

Agreed we should be using Jpeg XL :P

Both huge wins