2025/12/10

Newest at the top

2025-12-10 20:40:49 +0100ljdarj1ljdarj
2025-12-10 20:40:49 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 264 seconds)
2025-12-10 20:38:47 +0100ljdarj1(~Thunderbi@user/ljdarj) ljdarj
2025-12-10 20:36:06 +0100 <monochrom> In this case, "platform" means Linux vs Windows vs MacOS vs BSD vs...
2025-12-10 20:34:32 +0100ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-12-10 20:32:55 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 240 seconds)
2025-12-10 20:31:46 +0100Lord_of_Life(~Lord@user/lord-of-life/x-2819915) Lord_of_Life
2025-12-10 20:31:20 +0100Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 244 seconds)
2025-12-10 20:28:21 +0100 <tomsmeding> milan: that should indeed be true. Although these functions in particular you should probably get from System.IO instead of GHC.IO.StdHandles
2025-12-10 20:27:43 +0100machinedgod(~machinedg@d75-159-126-101.abhsia.telus.net) (Ping timeout: 240 seconds)
2025-12-10 20:20:15 +0100 <milan> tomsmeding: But this does not prevent using different backend (native, LLVM, c ...) right? Only different compiler altogether like "hugs"?
2025-12-10 20:20:08 +0100ljdarj1ljdarj
2025-12-10 20:20:07 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 240 seconds)
2025-12-10 20:16:23 +0100ljdarj1(~Thunderbi@user/ljdarj) ljdarj
2025-12-10 20:15:13 +0100cyphase(~cyphase@user/cyphase) cyphase
2025-12-10 20:13:51 +0100cyphase(~cyphase@user/cyphase) (Read error: Connection reset by peer)
2025-12-10 20:13:27 +0100 <tomsmeding> although with GHC being essentially the only realistic compiler for Haskell for the past decade(s?), these metadata fields are not always filled in quite as diligently as one might hope
2025-12-10 20:12:33 +0100 <tomsmeding> the Portability field in the module metadata is for portability across compilers. The stuff under "GHC." is, unsurprisingly, not at all portable to compilers other than GHC.
2025-12-10 20:11:01 +0100 <milan> Hello guyz why https://hackage.haskell.org/package/base-4.21.0.0/docs/GHC-IO-StdHandles.html has "Portability non-portable" specified when it's purpose is to be portable? This is written in docs "This model abstracts away the platform specific handles that can be toggled through the RTS."
2025-12-10 20:10:00 +0100milan(~milan@88.212.61.169)
2025-12-10 20:07:59 +0100kuribas(~user@2a02:1808:e7:7fdf:840:a1e:53dc:e766) (Ping timeout: 244 seconds)
2025-12-10 20:01:29 +0100ChaiTRex(~ChaiTRex@user/chaitrex) ChaiTRex
2025-12-10 20:00:34 +0100farn__(~farn@2a03:4000:7:3cd:d4ab:85ff:feeb:f505) farn
2025-12-10 19:59:57 +0100farn__(~farn@2a03:4000:7:3cd:d4ab:85ff:feeb:f505) (Ping timeout: 250 seconds)
2025-12-10 19:58:24 +0100ChaiTRex(~ChaiTRex@user/chaitrex) (Quit: ChaiTRex)
2025-12-10 19:47:05 +0100gmg(~user@user/gehmehgeh) (Quit: Leaving)
2025-12-10 19:41:19 +0100ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-12-10 19:35:30 +0100ephemient(uid407513@user/ephemient) ephemient
2025-12-10 19:32:45 +0100kuribas(~user@2a02:1808:e7:7fdf:840:a1e:53dc:e766) kuribas
2025-12-10 19:32:31 +0100kuribas(~user@2a02:1808:e7:7fdf:108a:7b48:1ca0:3c37) (Remote host closed the connection)
2025-12-10 19:29:41 +0100tromp(~textual@2001:1c00:3487:1b00:fc9c:738b:219c:bafe)
2025-12-10 19:21:37 +0100tromp(~textual@2001:1c00:3487:1b00:fc9c:738b:219c:bafe) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-12-10 19:20:43 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 264 seconds)
2025-12-10 19:12:02 +0100kuribas(~user@2a02:1808:e7:7fdf:108a:7b48:1ca0:3c37) kuribas
2025-12-10 19:07:49 +0100szkl(uid110435@id-110435.uxbridge.irccloud.com) (Quit: Connection closed for inactivity)
2025-12-10 19:04:11 +0100target_i(~target_i@user/target-i/x-6023099) target_i
2025-12-10 18:54:40 +0100jmcantrell_(~weechat@user/jmcantrell) jmcantrell
2025-12-10 18:49:30 +0100skum(~skum@user/skum) skum
2025-12-10 18:48:57 +0100 <larsivi> Hah, maybe I'm just a colorful person! I suppose I'll find some neovimmy place to ask :) Thanks! I'm sure I'll be back with other questions when I get into actual Haskell issues.
2025-12-10 18:40:47 +0100__monty__(~toonn@user/toonn) toonn
2025-12-10 18:37:07 +0100 <haskellbridge> <Morj> Wow, comparing them side by side right now, today I wouldn't make the choice to use haskell-vim, the default colors are just fine
2025-12-10 18:36:40 +0100wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2025-12-10 18:31:27 +0100 <haskellbridge> <Morj> Your original problem was that the haskell-vim colors look like the original colors?
2025-12-10 18:30:35 +0100 <haskellbridge> <Morj> My fork of haskell-vim also hasn't been updated in how many years and still works, so I doubt that /that/ is the problem
2025-12-10 18:29:00 +0100tromp(~textual@2001:1c00:3487:1b00:fc9c:738b:219c:bafe)
2025-12-10 18:26:49 +0100 <larsivi> Morj: There are default colors, but only a couple of elements in vague colors. Since haskell-vim hasn't been updated in a few years, I thought that could be a reason too. I suppose I have LSP via haskell-tools, but it hasn't brought a lot of colors (yet!)
2025-12-10 18:26:33 +0100tromp(~textual@2001:1c00:3487:1b00:fc9c:738b:219c:bafe) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-12-10 18:25:32 +0100elarks1elarks
2025-12-10 18:20:33 +0100wootehfoot(~wootehfoo@user/wootehfoot) (Quit: Leaving)
2025-12-10 18:17:34 +0100 <dolio> I don't recall the details, though.