I personally don't use Flatpak VSCode anymore, since I switched from Fedora Silverblue to Bluefin. I'll leave the instructions here for those who want them, but be aware that Flatpak VSCode instructions won't be maintained anymore.
WARNING
Note on FFI Interface Stability The current Foreign Function Interface (FFI) in Lean 4 was primarily designed for internal use within the Lean compiler and runtime. As such, it should be considered unstable. The interface may undergo significant changes, refinements, and extensions in future versions of Lean. Developers using the FFI should be prepared for potential breaking changes and should closely follow Lean's development and release notes for updates on the FFI system.
Atomic linking is at the heart of HVM's implementation: it is what allows threads to collaborate towards massive parallelism. All major HVM versions started with a better atomic linker. From slow, buggy locks (HVM1), to AtomicCAS (HVM1.5), to AtomicSwap (HVM2), the algorithm became simpler and faster over the years.
On the initial HVM3 implementation, I noticed that one of the cases on the atomic linker never happened. After some reasoning, I now understand why, and
Originally taken from
FileFormat.wiki
from the puz project.
PUZ is a file format commonly used by commercial software for crossword puzzles. There is, to our knowledge, no documentation of the format available online. This page (and the implementations) is the result of a bit of reverse engineering work.
| #r "nuget: FsToolkit.ErrorHandling" | |
| open FsToolkit.ErrorHandling | |
| open System | |
| type SensorReadings = int | |
| module RegularApproach = |
Distrobox init file which will create a container with asdf and the required tooling for one to build elixir/erlang (based on Fedora).
It is expected of the user to have brew installed on their system.
Instead of installing asdf onto the container, brew install asdf can be used to install it even outside of the container.
