Clarify Rust memory-ordering semantics for ARM64 concurrency patterns.
npx skills add https://github.com/po4yka/RIPDPI --skill memory-model-po4yka
Please help me install this Agent Skill. Skill: memory-model Source: https://github.com/po4yka/RIPDPI/tree/main/.claude/skills/memory-model Command: npx skills add https://github.com/po4yka/RIPDPI --skill memory-model-po4yka
Guiding developers through Rust memory ordering on ARM64 Android, focusing on happens-before reasoning, ordering constraints, and fence usage to prevent data races.
Review your concurrent Rust code and apply the recommended memory-ordering rules to ensure correctness on ARM64.
High-intent search queries and answers about installing and using this skill.
Choosing the correct Rust memory ordering on ARM64 requires applying happens-before reasoning to Relaxed, Acquire, Release, AcqRel, and SeqCst operations. This ensures proper visibility and synchronization for safe cross-thread communication.
Acquire ordering ensures subsequent reads see modifications made before a corresponding Release store. This pairing establishes a happens-before relationship, preventing data races by guaranteeing visibility of shared state across threads.
SeqCst provides a global total order for all sequentially consistent operations, while AcqRel only applies acquire and release semantics locally. SeqCst is necessary when cross-thread synchronization requires a universally agreed-upon operation sequence.
Placing memory fences in Rust involves inserting Acquire and Release barriers to enforce visibility ordering without blocking execution. Proper fence placement establishes happens-before relationships, preventing data races in concurrent Rust code.
Relaxed memory ordering does not inherently cause data races, but it provides no synchronization or ordering guarantees. It is safe only for independent atomic counter increments where cross-thread visibility of surrounding memory operations is unnecessary.
rainoftimeDetect data races in concurrent programs using dynamic and static analysis.
po4ykaConfigure a Telegram MTProto WS tunnel in RIPDPI with rustls or BoringSSL backends.
mohitmishra786Diagnose data races and deadlocks in C++ and Rust code.
Mte90Explain Rust concurrency patterns including threads, async, and synchronization primitives.
