When an agent missed a trap, its exchange could be emptied. The spec’s pricing formula also had a rounding bug, and none shipped a fix, even the ones that spotted it
https://t.co/1RynpXGcPm
The task was to build a small token exchange, with three traps: permissions can be kept and reused later, callers can swap out which implementation of an interface runs, and errors are lazy (with love from Haskell)
Coding agents sound just as confident when they’re wrong. I designed a small language with deliberately surprising semantics to see which agents check how it actually behaves, and which just assume.
https://t.co/1RynpXGcPm
Can the compiler handle linear state for us? Yes, by teaching linear logic to type class constraints. Written up in an #ICFP 2021 submission by Jean-Philippe Bernardy, @RaeHaskell, @Lowert, @aspiwack, and @nicolasgwu (3/5)
https://t.co/HEOoiJyivw
@mpeytonjones@tweagio The main issue with implicit params is that you have to name them, such as "?x". If you want to use them to represent an "open file" capability for example, then maybe you call this capability "?open". But now you can't have multiple open files, as their tokens' name would clash!
Linear types in Haskell, research phase 2: https://t.co/iczbH0vO9X. This time we're focusing on much improved developer experience. Linear type class constraints are the secret sauce.