Contributor to an open source project near you (Alpine Linux, Guix, ...). Passionate about functional programming (mostly Scheme and Haskell), software security, and operating systems. Day job in computer science, currently doing a postdoc in systems research.
Contributor to an open source project near you (Alpine Linux, Guix, ...). Passionate about functional programming (mostly Scheme and Haskell), software security, and operating systems. Day job in computer science, currently doing a postdoc in systems research.
Posts
Contributor to an open source project near you (Alpine Linux, Guix, ...). Passionate about functional programming (mostly Scheme and Haskell), software security, and operating systems. Day job in computer science, currently doing a postdoc in systems research.
Contributor to an open source project near you (Alpine Linux, Guix, ...). Passionate about functional programming (mostly Scheme and Haskell), software security, and operating systems. Day job in computer science, currently doing a postdoc in systems research.
Contributor to an open source project near you (Alpine Linux, Guix, ...). Passionate about functional programming (mostly Scheme and Haskell), software security, and operating systems. Day job in computer science, currently doing a postdoc in systems research.
There is a fun footgun related to compile-time code generation using procedural macros in Rust: if the macro has non-deterministic behavior, then the build process of any crate using it is not reproducible.
Here's a little write-up explaining how I uncovered such an issue in the hashify crate while trying to package Rust software for Guix: https://notes.8pit.net/notes/iqfs.html