Miles Frain

Also worth noting that the Euler example is the springboard for the book's [Getting Started](https://book.purescript.org/chapter2.html) chapter. We then work through `diagonal` together. So implementing this suggestion would also require some...

> which could use a little love to make it more user-friendly PR for that here: https://github.com/purescript-halogen/purescript-halogen-template/pull/26

A follow-up task is to document our recommended workaround in Contributing.md. Will do that after #228.

For those who know what they're looking for in the cookbook and are familiar with tagless-final style, this recipe may be helpful. But another target audience of the cookbook are...

I'm definitely in the enable-all-warnings camp, and would prefer to rename a shadowed variable rather than risk a bug. Giving users a choice about this via a compiler flag or...

I'm still a fan of the shadowing warnings, but wanted to note for completeness that fixing shadowing puts a damper on using record pun shorthand: ```purs -- Concise with shadowing...

Here's another example: ```purs type Stuff = { foo :: forall a. a -> a } broken :: Stuff -> Int broken { foo } = 5 where bar =...

And another example: ```purs type Stuff = { foo :: forall a. a -> a , bar :: forall a. a -> a } broken :: Stuff -> Int broken...

It turns out that `let` is unrelated to this issue. Here are some even simpler examples: ```purs type Stuff = { foo :: forall a. a -> a , bar...

Is the following compilation failure considered the same bug, or a new bug? It is unique from the previous examples in this thread in that using a named pattern is...