Nathan Faubion

> Something I noticed recently is that there isn't a kind Int there. And if there was, it has a conflict with the type Int. There is no kind Int....

`true` and `false` are reserved keywords. The identifier rules are the same for term and type level. You can't bind `true` as a type variable. There's no reason the `true`...

> And wasn't True/False at the value-level avoided because those values aren't actual ADTs? I guess? But we pattern match on them as an ADT, so the distinction seems completely...

FWIW, this is something that's been requested several times in IRC by various people. It would be a really nice thing to have for custom Preludes to prevent name clashes....

ie ```purescript module A (export Data.Map as Map) where module B where import A ``` ```purescript module A (export Data.Map as Map) where module B where import A import Data.Map...

I've been using purs-ide auto imports for the past few years, and I've consequently stopped caring about import boilerplate. Is this something still worth discussing? Should this be in "Ideas"...

> Is purs-backend-es already that no-regrets tool for codegen? purs-backend-es does not subsume compiler functionality. * It is not incremental, so right now it's largely targeted at production builds. If...

Additionally, halogen-vdom only fires `ref` handlers on element creation and removal. If you don't have a `ref`, and then add one after the element has already mounted, it won't fire....

Actually, I take that back! It should work as expected on the vdom side, as `applyProp` is used in both `render` and `patch`. https://github.com/slamdata/purescript-halogen-vdom/blob/master/src/Halogen/VDom/DOM/Prop.purs#L128

Woah I can close tickets across repos 😮