New week, new Rust! What are you folks up to?
For no very good reason I decided to implement pstd::Arc. was struggling to "grok" acquire/release, so watching this video and I think I just "got it".
"If an atomic store in thread A is tagged memory_order_release, an atomic load in thread B from the same variable is tagged memory_order_acquire, and the load in thread B reads a value written by the store in thread A, then the store in thread A synchronizes-with the load in thread B."
Working on Accent, a static site generator / CMS with WASM plugins.
And on Driller, a load testing tool with YAML test plans.
Creating a more unrestricted compile time reflection workaround, F_Comptime :]
It already unlocks more possibilities and flexibilities. Now figuring how to make knowing parameter types, parameter values, generic types, generic values possible
I have the design to expand the macro to parse the types, and wrap the callers inside macro too to get the ::< > types and values, then combines them into table, then stores them to static variable that only exist in comptime mode or temporary files, then it can be used inside the comptime logic
Then the code gets cleaned in normal compilation
Working on getting Rust code to run on iOS through UniFFI for the Paperback Ebook reader project (https://paperback.dev). The core and the desktop app are all written in Rust, with thin native Kotlin/Swift layers for mobile apps.
Found out that making file-backed data structures may be easy[1], by rewriting HyperLogLog with memory-mapped accesses (view at filebacked-ds/src/main.rs at 653f0ffb0f0da1c0bd16fcb1f4fd49eb9d1b6b3e · ProgramCrafter/filebacked-ds · GitHub).
for DS which don't have indirection ↩︎
Drugwars - rust port of an old classic.