I’ve just noticed that there’s a dark stain on my wall, I think it might be from the time I installed the lamp and cut my finger while removing insulation from the wires; but I thought I cleaned it up long ago. WTF @bl00d reference?!
There’s a proof assistant called Isabelle; the most used part is Isabelle/HOL (which stands for High Order Logic) but there’s also Isabelle/FOL (First Order Logic), and apparently there are also people named “Isabelle Fol”, which makes searching a bit complicated :blobcatnotlikethis:
This day’s frustrating debugging session sponsored by shitty error handling in <stdlib.h>, namely that atoi(garbage) == 0 and so it’s not straightforward to tell if the 0 was there or not :cirno_for_reals:
@Ukko It's weird that it just shows empty on Disqordia tbh, when I look at something from my allowlist instance quoted from a domain that's not on the list it shows as "quoted status unavailable". Maybe it's different when you're the one blocked.
You can opt out of Yassy Pat entirely by adding #nopat to your profile bio, or by sending Yaseen a request privately. Opt out isn’t as conservative as opt in, but opt in results in far fewer users, and users are critical for patting to be useful. Yassy Pat has no indexing or search, so hopefully this is a reasonable tradeoff.
I could buy an used Thrustmaster eSwap for the price of a new Xbox controller; I usually prefer to buy new things and use them until they break (and if it’s used I don’t know how badly was it treated by the previous owner), but this one has replaceable parts, so if a stick breaks or something it’s not the end of the world.
Unfortunately, from what I read online it looks like it’s not supported on anything other than Windows; meanwhile Xbox controllers work fine on Linux and Mac.
It continues to amaze me that if you want something to work on a non-Windows platform then hardware made by Microsoft is usually a safer bet :cirno_for_reals:
$ rustc -O --target=wasm32-unknown-unknown <a href="http://main.rs" rel="ugc">main.rs</a> -o main.wasm
error: `#[panic_handler]` function required, but not found
error: aborting due to 1 previous error
QBE seems a lot more understandable https://c9x.me/compile/doc/il.html
Though it’s a bummer that there aren’t any atomic and vector instructions (?)
It’s not like I need any of that right now, but it bugs me that if I start with QBE I’m going to hit a ceiling sooner or later.
Maybe it would be easy to move to LLVM later since it’s also SSA, or maybe even contribute some code to QBE myself? I don’t have anything to test the risc64 backend though.
I should probably start actually doing something instead of screwing around and poring over possibilities.
@subtype if i recall the spec (and it has been a while) wasm really only defines kinda normal cpu logic, and then tries to store the control flow graph in a structured form (because they hate gotos, and don't want the wasm runtimes to have to recover the control flow graph when transpiling), and things like AVX instructions are exiled to being functions you import from the runtime (like it works for GCC intrinsics) and they turn it in to what it should be, if they can, on their end.