wen @cyrridven@computerfairi.es

Listen, I just watched The Favourite, and I've been playing too much MtG these past days, so this was unavoidable.

Listen, I just watched The Favourite, and I've been playing too much MtG these past days, so this was unavoidable.

Me, the evening before my talk: "Ah, I've got my colour scheme down!"

Reading the Agda source like...

YOU CAN DO THAT?

Maybe, instead of shitposting, I should go and finish preparing my own talk...?

Looking forward to Jurriaan's talk tomorrow at the Haskell Symposium!

Also, the links in the announcement are broken, even though they're fixed on the web branch, but frustratingly I can't seem to get GitHub to refresh the site!

There's a couple of rough edges to the generated documents, and patches to the compilation process are very, very welcome!

PLFA is now available as a PDF and an EPUB! #PLFA #Agda

[PDF]: https://plfa.github.io/plfa.pdf
[EPUB]: https://plfa.github.io/plfa.epub

I'm using not using pandoc-citeproc as a command-line utility, but rather I'm using it as a library to read CSL and BibTeX files, and process the citations in a Pandoc document. But it's getting to out of date not to make the switch soon.

Does anyone know how I migrate from #Pandoc's old pandoc-citeproc to the newer citeproc? #Haskell

If I use the keyboard she swats at me and sleep-growls

Getting work done like

Hey #Racket Twitter! Can I use #PLTRedex with an SMT solver? Via z3-rkt or Rosette? They all use different languages, and I don't know enough about Racket to see if there's any way to make that work.

It currently explicitly says there's no type 'prop' of propositions, but adding an explicitly classical prop would make that... very possible 🤩

Wonder if that opens up the door to specify proofs in the same language!

I should've actually looked at SMT-LIB 3.0 way sooner! They're moving to a dependently-typed language! I'm way more excited now!

Just wanna vent and say that @RoyalMailHelp@twitter.com is shite and I really wished they'd stop losing my packages.

Heya PL twitter! Without peeking, which of the following properties do you think hold for floating-point arithmetic?
https://forms.gle/Ui9e6cguuxAAfg8h7

Can anyone help me resolve these seemingly contradictory statements in the IEEE spec for floats?