Khám phá bài viết phân tích chi tiết các lỗi truy cập dữ liệu (data race) phổ biến trong Go và cách tránh chúng. Tác giả /u/broken_broken_ trên Reddit chia sẻ góc nhìn về rủi ro và bài học khi lập trình đa luồng. #GoLang #Concurrency #LapTrinhGo #DataRace
[None]
https://www.reddit.com/r/programming/comments/1p65upq/a_million_ways_to_die_from_a_data_race_in_go/
🚀 Going to ISC 2025? Join us for “GORC: A Graph Neural Network-Based Static Data Race Checker for OpenMP”
📅 June 12 | 🕐 13:25–13:50 | 📍 Hall F, 2nd Floor, Hamburg Congress Center
Speakers Anh Tran & Ignacio Laguna unveil GORC, a novel GNN-based race checker trained on PrograML graphs.
GORC achieves higher recall than LLOV and handles incomplete programs, outperforming current ML-based tools.
https://isc-hpc.com/program/schedule
#ISC25 #OpenMP #DataRace #HPC #StaticAnalysis #GraphNeuralNetwork
🤓 Ah yes, the brave soul who attempts to explain 'Atomics and Concurrency' while sounding like they're deciphering the Rosetta Stone of tech. 📜 Don’t worry, just enable the ⚠️ #TSan flag and enjoy the thrilling life of a data race spectator! 🎢
https://redixhumayun.github.io/systems/2024/01/03/atomics-and-concurrency.html #Atomics #Concurrency #DataRace #TechHumor #HackerNews #ngated
Is the #clock still #ticking or has #time run out?
https://www.folkifiedpoprageousness.com/2024/05/tick-tock-tiktok.html
#Brainstorm #Neuralink #SocialMedia #dataRace #everythingApp #Elysium #strangeDays indeed Most #Peculiar #Mamma #JohnLennon
#ColdWar Kids #Styx off #KilroyWasHere #MuzakLessons #AGI #dataRace
#Informatic overload continue #processing
My Best and Worst #Deadlock in #Rust - by snoyman
https://www.snoyman.com/blog/2024/01/best-worst-deadlock-rust/
Really great read! I didn't know that about `RwLock`. 🤯
"Benign Data Races: What Could Possibly Go Wrong?" [2013], Intel (https://software.intel.com/content/www/us/en/develop/blogs/benign-data-races-what-could-possibly-go-wrong.html).
On /r/programming: https://old.reddit.com/r/programming/comments/19rtbn/benign_data_races_what_could_possibly_go_wrong/
See also: A series of articles by Russ Cox (https://research.swtch.com/mm) on memory-models.
@luna You gotta newtype it. Rawpointers are !Send + !Sync because if you access through them wrong from multiple threads, you will cause a #DataRace and #WakeTheDragon.
If you haven't already, you should read the Nomicon before doing unsafe things: https://doc.rust-lang.org/nomicon/
