Logs: liberachat/#haskell
| 2025-11-19 10:10:45 | × | myxokephale quits (~myxos@2001:579:8380:f20:a23e:fff0:9e97:fbf) (Ping timeout: 265 seconds) |
| 2025-11-19 10:14:32 | → | myxos joins (~myxos@wsip-70-166-126-146.ph.ph.cox.net) |
| 2025-11-19 10:17:06 | × | trickard quits (~trickard@cpe-62-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2025-11-19 10:17:20 | → | trickard_ joins (~trickard@cpe-62-98-47-163.wireline.com.au) |
| 2025-11-19 10:19:17 | × | deptype quits (~deptype@2406:b400:3a:9d2f:bc62:5450:375:9b3f) (Remote host closed the connection) |
| 2025-11-19 10:19:31 | → | deptype joins (~deptype@2406:b400:3a:9d2f:a44b:c20f:51e9:62bc) |
| 2025-11-19 10:29:33 | → | kuribas joins (~user@ip-188-118-57-242.reverse.destiny.be) |
| 2025-11-19 10:31:02 | × | trickard_ quits (~trickard@cpe-62-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2025-11-19 10:31:15 | → | trickard_ joins (~trickard@cpe-62-98-47-163.wireline.com.au) |
| 2025-11-19 10:35:47 | <probie> | can you get away with a top level IORef (with the NOINLINE unsafePerformIO shenangians)? |
| 2025-11-19 10:39:23 | × | deptype quits (~deptype@2406:b400:3a:9d2f:a44b:c20f:51e9:62bc) (Remote host closed the connection) |
| 2025-11-19 10:39:42 | → | deptype joins (~deptype@2406:b400:3a:9d2f:a8bf:8a15:2c9c:d5b2) |
| 2025-11-19 10:41:07 | <haskellbridge> | <Morj> I believe this is a common pattern in some situations, like for logging |
| 2025-11-19 10:42:07 | × | m1dnight quits (~m1dnight@d8D861A17.access.telenet.be) (Ping timeout: 240 seconds) |
| 2025-11-19 10:44:10 | → | fp1 joins (~Thunderbi@2001:708:150:10::7e06) |
| 2025-11-19 10:44:17 | × | fp quits (~Thunderbi@wireless-86-50-140-28.open.aalto.fi) (Quit: fp) |
| 2025-11-19 10:44:17 | fp1 | is now known as fp |
| 2025-11-19 10:45:10 | → | ubert1 joins (~Thunderbi@178.165.175.248.wireless.dyn.drei.com) |
| 2025-11-19 10:45:15 | × | qqe quits (~qqq@185.54.21.140) (Remote host closed the connection) |
| 2025-11-19 10:47:14 | → | m1dnight joins (~m1dnight@d8D861A17.access.telenet.be) |
| 2025-11-19 10:58:35 | → | CiaoSen joins (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) |
| 2025-11-19 10:59:09 | <tomsmeding> | probie: yes, if the only thing in unsafePerformIO is the creation of the IORef and the usages are in normal IO, that's fine |
| 2025-11-19 10:59:24 | × | deptype quits (~deptype@2406:b400:3a:9d2f:a8bf:8a15:2c9c:d5b2) (Remote host closed the connection) |
| 2025-11-19 10:59:41 | → | deptype joins (~deptype@2406:b400:3a:9d2f:445f:7a99:cca5:e330) |
| 2025-11-19 10:59:45 | <tomsmeding> | if you do mutations to the IORef also in unsafePerformIO, if I'm not mistaken it is prudent to add {-# OPTIONS -fno-cse -fno-full-laziness #-}, but this may be cargo-culting |
| 2025-11-19 10:59:50 | → | humasect joins (~humasect@dyn-192-249-132-90.nexicom.net) |
| 2025-11-19 11:04:24 | × | humasect quits (~humasect@dyn-192-249-132-90.nexicom.net) (Ping timeout: 244 seconds) |
| 2025-11-19 11:08:10 | × | bggd quits (~bgg@2a01:e0a:819:1510:3dbd:4461:e226:b31) (Remote host closed the connection) |
| 2025-11-19 11:08:31 | × | X-Scale quits (~ARM@6.67.114.89.rev.vodafone.pt) (Ping timeout: 240 seconds) |
| 2025-11-19 11:12:24 | × | _d0t quits (~{-d0t-}@user/-d0t-/x-7915216) (Remote host closed the connection) |
| 2025-11-19 11:13:15 | → | _d0t joins (~{-d0t-}@user/-d0t-/x-7915216) |
| 2025-11-19 11:13:49 | → | xff0x joins (~xff0x@2405:6580:b080:900:a3f:66bc:6216:f05b) |
| 2025-11-19 11:16:40 | → | X-Scale joins (~ARM@6.67.114.89.rev.vodafone.pt) |
| 2025-11-19 11:19:56 | × | deptype quits (~deptype@2406:b400:3a:9d2f:445f:7a99:cca5:e330) (Remote host closed the connection) |
| 2025-11-19 11:20:13 | → | deptype joins (~deptype@2406:b400:3a:9d2f:75a6:1ebe:81f5:e9d6) |
| 2025-11-19 11:22:13 | × | vardhan quits (~vardhan@122.172.80.248) (Ping timeout: 264 seconds) |
| 2025-11-19 11:23:55 | → | vardhan joins (~vardhan@122.172.85.143) |
| 2025-11-19 11:32:43 | <yin> | jreicher: tree-sitter highlight enabled: https://shot.jrvieira.com/1763551807.png vs disabled: https://shot.jrvieira.com/1763551862.png |
| 2025-11-19 11:33:13 | <yin> | former is very inconsistent, even for trivial syntax like this |
| 2025-11-19 11:33:30 | × | srazkvt quits (~sarah@user/srazkvt) (Read error: Connection reset by peer) |
| 2025-11-19 11:33:55 | × | vardhan quits (~vardhan@122.172.85.143) (Ping timeout: 264 seconds) |
| 2025-11-19 11:34:38 | <jreicher> | Why do you think it's inconsistent? It's giving you more grammatical information, which is why it looks different. You can set it to give less if you want. |
| 2025-11-19 11:34:39 | → | deptype_ joins (~deptype@124.123.133.153) |
| 2025-11-19 11:35:06 | <jreicher> | Set `treesit-font-lock-level' to a smaller number |
| 2025-11-19 11:35:16 | → | vardhan joins (~vardhan@122.172.81.68) |
| 2025-11-19 11:36:53 | <jreicher> | There's also even more fine grained control if you want. |
| 2025-11-19 11:37:16 | × | deptype quits (~deptype@2406:b400:3a:9d2f:75a6:1ebe:81f5:e9d6) (Ping timeout: 264 seconds) |
| 2025-11-19 11:37:39 | <yin> | it gets worse on more complex syntax. this was what i had in front of me. how do we explain the highlighting of `constant` in the signature? |
| 2025-11-19 11:39:56 | <jreicher> | Oh I think I see what you mean. Hmm. That might be a bug. What version of the treesitter grammar are you using? And also what version of Emacs? |
| 2025-11-19 11:45:01 | <yin> | it's nvim v0.11.5. not sure how to check the grammar version |
| 2025-11-19 11:45:39 | <jreicher> | Oh! I'm so sorry, I shouldn't have assumed you were using Emacs. |
| 2025-11-19 11:48:42 | × | gmg quits (~user@user/gehmehgeh) (Remote host closed the connection) |
| 2025-11-19 11:49:01 | <__monty__> | I'm actually more confused about the different coloring for identifiers in the other signatures. |
| 2025-11-19 11:49:17 | <__monty__> | Also the definition of `pure` though. |
| 2025-11-19 11:49:25 | → | gmg joins (~user@user/gehmehgeh) |
| 2025-11-19 11:49:36 | <__monty__> | And speed and duration. |
| 2025-11-19 11:50:35 | → | jjhoo joins (~jahakala@user/jjhoo) |
| 2025-11-19 11:50:46 | <jreicher> | yin: you might want to ask on #neovim. What you are seeing could be specific to the integration with treesitter, rather than treesitter itself, as treesitter doesn't actually do any highlighting; it just provides parsing information. |
| 2025-11-19 11:50:46 | <yin> | i'm checking other files and i think it has actually got much better than what i remember. but this specific bug is very noticeable on every file i'm checking. i can't find a pattern, it seems to randomly highlight some function names in signatures differently |
| 2025-11-19 11:51:38 | <jreicher> | It's possible there's a bug in the parse, but I think that would be less likely. I am guessing though. |
| 2025-11-19 11:52:25 | × | califax quits (~califax@user/califx) (Remote host closed the connection) |
| 2025-11-19 11:52:27 | <yin> | jreicher: ok thanks |
| 2025-11-19 11:53:17 | <yin> | __monty__: is the definition of `pure` wrong? |
| 2025-11-19 11:53:59 | <yin> | i'm just starting out trying to understand the basics of FRP |
| 2025-11-19 11:54:44 | → | califax joins (~califax@user/califx) |
| 2025-11-19 11:55:46 | → | srazkvt joins (~sarah@user/srazkvt) |
| 2025-11-19 11:57:45 | <__monty__> | No, just talking about the highlighting here. Identifiers are green in definitions but pure, speed and duration are white? The latter at least also have a signature but coloring identifiers a different color in signatures is also weird to me. For types and constructors the distinction makes sense but not for other identifiers. |
| 2025-11-19 12:04:29 | × | Inline quits (~inlinE@2001-4dd7-ae97-0-4674-ae6d-2607-c022.ipv6dyn.netcologne.de) (Remote host closed the connection) |
| 2025-11-19 12:04:35 | <yin> | ah, yes |
| 2025-11-19 12:07:13 | trickard_ | is now known as trickard |
| 2025-11-19 12:15:03 | × | driib318 quits (~driib@vmi931078.contaboserver.net) (Ping timeout: 250 seconds) |
| 2025-11-19 12:17:37 | × | Enrico63 quits (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) (Quit: Client closed) |
| 2025-11-19 12:18:21 | → | driib318 joins (~driib@176.57.184.141) |
| 2025-11-19 12:19:59 | → | Guest73 joins (~Guest73@60-249-14-96.hinet-ip.hinet.net) |
| 2025-11-19 12:20:04 | × | Guest73 quits (~Guest73@60-249-14-96.hinet-ip.hinet.net) (Client Quit) |
| 2025-11-19 12:21:04 | × | lucabtz quits (~lucabtz@user/lucabtz) (Ping timeout: 264 seconds) |
| 2025-11-19 12:23:23 | <haskellbridge> | <Morj> Yeah, in general I find people go too crazy with syntax-based highlighting, I just rely on vim's regex-based, it's less shouty |
| 2025-11-19 12:23:38 | <haskellbridge> | <Morj> https://tonsky.me/blog/syntax-highlighting/ - was a good article about that recently |
| 2025-11-19 12:24:09 | × | driib318 quits (~driib@176.57.184.141) (Ping timeout: 265 seconds) |
| 2025-11-19 12:24:25 | <haskellbridge> | <Morj> The biggest sillyness was zig, that on their official docs highlighted all identifiers in yellow. But everything is an identifier! So all the code was yellow on grey |
| 2025-11-19 12:24:40 | <haskellbridge> | <Morj> They changed it since then |
| 2025-11-19 12:31:44 | → | driib318 joins (~driib@vmi931078.contaboserver.net) |
| 2025-11-19 12:32:59 | → | humasect joins (~humasect@dyn-192-249-132-90.nexicom.net) |
| 2025-11-19 12:33:04 | <probie> | tomsmeding: sorry, that wasn't really a question, that was meant to be in response to [exa]'s question (re: global state in wasm) |
| 2025-11-19 12:34:15 | <[exa]> | probie: oh whops I missed that, thanks! |
| 2025-11-19 12:34:28 | <[exa]> | so, well, let's see if that crashes the wasm runner. :D |
| 2025-11-19 12:35:36 | × | tromp quits (~textual@2001:1c00:3487:1b00:8d4:6354:928b:6095) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2025-11-19 12:36:33 | → | tromp joins (~textual@2001:1c00:3487:1b00:8d4:6354:928b:6095) |
| 2025-11-19 12:36:40 | → | leosha joins (~leoshatru@58.164.30.38) |
| 2025-11-19 12:36:49 | <leosha> | @free x :: Int |
| 2025-11-19 12:36:49 | <lambdabot> | x = x |
| 2025-11-19 12:37:00 | <leosha> | @free forall f. Functor f => (a -> f b) -> s -> f t |
| 2025-11-19 12:37:00 | <lambdabot> | Try `free <ident>` or `free <ident> :: <type>` |
| 2025-11-19 12:37:13 | <leosha> | @free x :: forall f. Functor f => (a -> f b) -> s -> f t |
| 2025-11-19 12:37:13 | <lambdabot> | Extra stuff at end of line |
| 2025-11-19 12:37:23 | <leosha> | @free x :: forall f. Functor f => (a -> f b) -> s -> f t |
| 2025-11-19 12:37:23 | <lambdabot> | Extra stuff at end of line |
| 2025-11-19 12:37:35 | <leosha> | @free x :: forall f. Functor f => (a -> f b) -> s -> f t |
| 2025-11-19 12:37:35 | <lambdabot> | Extra stuff at end of line |
| 2025-11-19 12:37:44 | <tomsmeding> | @free x :: Functor f => (a -> f b) -> s -> f t |
All times are in UTC.