documentation VS iedit

The example from the PureScript documentation is:

Filippo: With Haskell knowledge, reading PureScript documentation was enough.

See https://github.com/purescript/documentation/blob/master/errors/TypesDoNotUnify.md for more information, or to contribute content related to this error.

[1 of 1] Compiling Main Error found: in module Main at src/Main.purs:40:35 - 40:39 (line 40, column 35 - line 40, column 39) Could not match type { age :: Maybe Int , name :: String , team :: Maybe String} with type Json while checking that type t0 is at least as general as type Json while checking that expression user has type Json in value declaration main where t0 is an unknown type See https://github.com/purescript/documentation/blob/master/errors/TypesDoNotUnify.md for more information, or to contribute content related to this error. [error] Failed to build.)

I'm trying to get a better grasp on the type system of purescript. One thing I'm struggling to fully understand is how the so-called "kind system" works. The language reference is very brief about it.

purescript uses (_ - 5) for that operator section, which i'm not a total fan of, but it's at least unambiguous; agda would write it as _- 5

The one page you should add to the documentation is "differences from Vim".

For example, https://github.com/purescript/documentation/blob/master/lang... makes picking up PureScript as a Haskell programmer much easier than having to read all of the documentation and do the diff yourself.

More info can be found here: https://github.com/purescript/documentation/blob/master/guides/Getting-Started.md

Try iedit https://www.emacswiki.org/emacs/Iedit.

Then, in *rg* buffer, we transform org-link-expand-abbrev into org-link-RENAMED the way we prefer (we have all the Emacs power, some of us might use query-replace, other might use multiple-cursors.el, other iedit, etc.). And so *rg* buffer looks like this:

I've discovered iedit, which allows me to C-; over any string and edit all occurrences of it simultaneously, à la multiple-cursors. The default behaviour is that, by pressing C-; only once, it selects all occurences of the string in the whole buffer. Is there a way to expand the selection to each new match one at a time? For those familiar with, I'm basically trying to replicate Sublime Text's functionality when you Ctrl/Cmd-D over any string.