Gary Burgess
Gary Burgess
@natefaubion is talking a good game on Slack, so I'll open an issue for it. Proposal is: 1. to introduce `forall`-before-the-constructor: `data Box = forall a. Box a` 2. to...
**Edit: There's a lot of commentary on this issue before [this issue is summarized by `rhendric`](https://github.com/purescript/purescript/issues/3493#issuecomment-882001403). Current discussion follows from that comment.** Opening an issue as a place to discuss...
Suggestion from @natefaubion. Something vaguely like: ``` purescript module MyPrelude ( module Data.Map as M ... ) where import Data.Map ``` Then you can: ``` purescript import MyPrelude myInsert =...
I think the PR that added pattern matching in let/where intentionally didn't do anything with this case, but: ``` purescript bug = result where result = x -- Unknown value...
When there's a definition like: ``` haskell parseJSON :: forall a. (ReadForeign a) => String -> Either String a parseJSON json = fromString json >>= parseForeign read where fromString ::...
I recently encountered a deadlock situation that I fixed by `fork`ing a `raise`. That should absolutely not be a thing. Will have to try and come up with a simple...
Given #646 and https://github.com/purescript-halogen/purescript-halogen/issues/629#issuecomment-548941920, maybe we could remove the automatic `Ref` tracking from the component machinery itself, and just have it as a kind of hook that raises an action...
Might be useful from time to time - there may be some cases where receiver and initializer would be one in the same. From a Slack discussion.
With `RowToList` we could have it so that the output messages for a component could be listened to with a record-like construct, like this: ``` purescript { onMessage1: handler ,...
With `RowToList` we use records rather than the current property arrays in the HTML DSL.