Newest at the top
| 2025-04-01 16:58:22 +0200 | <tomsmeding> | I don't know why ace.js thought it was a good idea to explicitly clear undo history when setting the contents of an edit session to a new srting |
| 2025-04-01 16:57:46 +0200 | <hellwolf> | tomsmeding: great! |
| 2025-04-01 16:57:33 +0200 | <EvanR> | metavariable |
| 2025-04-01 16:57:28 +0200 | <EvanR> | x is supposed to range over variables, not any pattern xD |
| 2025-04-01 16:57:04 +0200 | <EvanR> | let !K = e in body isn't an instance of the rule let !x = e in body, when you translate them you get different behaving results |
| 2025-04-01 16:56:57 +0200 | <tomsmeding> | hellwolf: https://github.com/haskell/play-haskell/commit/5630aaa0da9fb7ffaecf43fc526a8ff5024b5d84 the undo problem should be fixed now, in case you manage to be super fast anyway or if the button remains for whatever reason |
| 2025-04-01 16:56:21 +0200 | <EvanR> | alright I think my substitution failed |
| 2025-04-01 16:54:48 +0200 | mari-estel | (~mari-este@user/mari-estel) (Remote host closed the connection) |
| 2025-04-01 16:54:20 +0200 | gehmehgeh | (~user@user/gehmehgeh) gehmehgeh |
| 2025-04-01 16:54:15 +0200 | <tomsmeding> | `let !K = expr in _` is, however, strict in `expr` |
| 2025-04-01 16:54:12 +0200 | gmg | (~user@user/gehmehgeh) (Ping timeout: 264 seconds) |
| 2025-04-01 16:53:54 +0200 | <tomsmeding> | I used "pattern match" to refer to the first two, but that's ambiguous, I concede |
| 2025-04-01 16:53:25 +0200 | <tomsmeding> | `let K = expr in _` is _not_ strict in `expr` |
| 2025-04-01 16:53:02 +0200 | <tomsmeding> | the function `foo K = _` is strict in its argument |
| 2025-04-01 16:52:56 +0200 | Digitteknohippie | Digit |
| 2025-04-01 16:52:50 +0200 | <tomsmeding> | `case x of K -> _` is strict in x |
| 2025-04-01 16:52:21 +0200 | <EvanR> | I have no idea what you're saying xD |
| 2025-04-01 16:52:09 +0200 | <tomsmeding> | okay "pattern match" is indeed ambiguous wording |
| 2025-04-01 16:52:01 +0200 | <tomsmeding> | a let |
| 2025-04-01 16:51:50 +0200 | <EvanR> | or both |
| 2025-04-01 16:51:45 +0200 | <EvanR> | let K = ... is a pattern match or a let |
| 2025-04-01 16:51:25 +0200 | <tomsmeding> | it does _here_, but not in a pattern match, because pattern matches are strict and let is lazy |
| 2025-04-01 16:51:22 +0200 | jmcantrell | (~weechat@user/jmcantrell) jmcantrell |
| 2025-04-01 16:51:08 +0200 | <tomsmeding> | EvanR: no, I was complaining about your claim that the seq doesn't have any effect if x is a constructor pattern |
| 2025-04-01 16:51:04 +0200 | <EvanR> | lol what does `x' quantify over |
| 2025-04-01 16:50:52 +0200 | <EvanR> | or maybe it was only talking about variable bindings |
| 2025-04-01 16:50:38 +0200 | <EvanR> | tomsmeding, well that translation I gave is in the docs let !x = e in body ==> let x = e in x `seq` body. You're saying let !K = e in body is somehow different from let K = e in K `seq` body? |
| 2025-04-01 16:47:27 +0200 | longlongdouble | (~longlongd@2405:201:5c16:894:2d75:fd2d:c031:9b09) (Client Quit) |
| 2025-04-01 16:47:22 +0200 | longlongdouble | (~longlongd@2405:201:5c16:894:2d75:fd2d:c031:9b09) |
| 2025-04-01 16:47:18 +0200 | rit | (~rit@2409:40e0:101e:42e7:101c:ea47:4905:baf6) (Ping timeout: 240 seconds) |
| 2025-04-01 16:46:19 +0200 | <tomsmeding> | O.o |
| 2025-04-01 16:46:15 +0200 | <hellwolf> | in the new tab. yes. |
| 2025-04-01 16:46:08 +0200 | <tomsmeding> | the button disappears now for you? |
| 2025-04-01 16:46:00 +0200 | <hellwolf> | with a new tab |
| 2025-04-01 16:45:55 +0200 | <hellwolf> | no, I can't reproduce anymore |
| 2025-04-01 16:45:34 +0200 | gLLMguy | glguy |
| 2025-04-01 16:44:05 +0200 | <tomsmeding> | any errors in the javascript console? |
| 2025-04-01 16:43:54 +0200 | <tomsmeding> | it would be very weird if those don't fire for you |
| 2025-04-01 16:43:43 +0200 | <tomsmeding> | I'm attaching an event handler to the mousemove and keydown events, globally on the page |
| 2025-04-01 16:42:49 +0200 | <tomsmeding> | me too |
| 2025-04-01 16:42:21 +0200 | <hellwolf> | firefox |
| 2025-04-01 16:42:07 +0200 | <tomsmeding> | what browser are you using? |
| 2025-04-01 16:41:51 +0200 | <hellwolf> | I think it responds to input event. |
| 2025-04-01 16:41:34 +0200 | <hellwolf> | it shows up all the time for me |
| 2025-04-01 16:41:31 +0200 | <tomsmeding> | the fact that it was stil there for you means that that didn't work |
| 2025-04-01 16:41:22 +0200 | <tomsmeding> | the button is supposed to disappear after about 4 seconds after you interact with the page |
| 2025-04-01 16:40:43 +0200 | <hellwolf> | but I clicked the wrong button :/ |
| 2025-04-01 16:40:38 +0200 | <hellwolf> | I typed then I wanted to share. |
| 2025-04-01 16:39:56 +0200 | <tomsmeding> | or does it not disappear for you? |
| 2025-04-01 16:39:28 +0200 | <tomsmeding> | hellwolf: that C-z not working is a bug and I'll fix it, but how did you manage to type all that code before the button disappeared? |