documentation VS helix

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

Nice post. Obligatory Helix plug: For anyone interested in taking this further, there are whole editors designed around multi-cursor editing.

https://helix-editor.com/

I could never turn it off completely but I do sometimes use the Acme theme during the day (it's too bright in the evening), which highlights just comments, strings, and errors.

https://github.com/helix-editor/helix/wiki/Themes#acme

You can use a snippet LSP to work around Helix not having a built-in LSP manager. They're listed in https://github.com/helix-editor/helix/issues/395

I'm probably not the average python programmer.

But I normally just create two terminals (I have a tiling window manager) and in one I open a python file under /tmp/ write my code and execute it in the other terminal.

I would probably use a REPL if it was integrated in my favorite editor ( https://helix-editor.com ).

Wow, that's been there a while: https://github.com/helix-editor/helix/commit/35c974c9c49f912...

Wonder how I missed that. I'm getting a re-education in helix today -- thank you! I'll go through `hx --tutor` again before I insert any more feet in my mouth.

Interesting to see how they are gonna approach integrating plugins/extensions system, because this is likely gonna be one of the major factors affecting adoption and ecosystem growth.

Helix devs, for instance, lean towards a Scheme-like implementation. [1]

[1]: https://github.com/helix-editor/helix/discussions/3806#discu...