This is a feature request for
love.keyboard.wasDown. It would work exactly like
love.keyboard.isDown, except it returns true if one of the keys was pressed any time since the last update, instead of needing to be pressed at the exact moment the function is called.
Many times, it's more convenient to check lk.isDown from love.update instead of writing a love.keypressed handler. But this doesn't always work nicely. Suppose you can briefly tap a key to jump or fire; if you check for this with lk.isDown, it could easily miss... the player could press and release the key before the update fires, and in that case you'll never jump/fire.
If we introduce lk.wasDown, we could use that instead and the keypress would register. Additionally, calls to lk.wasDown could be paired with lk.isDown to determine whether a key was tapped and released, or was tapped and is still being held, all without love.keypressed being necessary.
This may sound trivial, but I've run into several cases now where "wasDown" would be preferable to "isDown." In some cases it's almost a necessity (e.g. non-intrusive library code without a huge API footprint), in others it's just a convenience. The same goes for love.mouse, really, but one thing at a time. :)