2025/07/31

Newest at the top

2025-07-31 18:03:33 +0200jmcantrell(~weechat@user/jmcantrell) (Ping timeout: 248 seconds)
2025-07-31 17:49:39 +0200poscat0x04(~poscat@user/poscat) (Ping timeout: 260 seconds)
2025-07-31 17:48:00 +0200tromp(~textual@2001:1c00:3487:1b00:b928:de3f:1dfd:983a)
2025-07-31 17:47:56 +0200poscat(~poscat@user/poscat) poscat
2025-07-31 17:44:07 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-07-31 17:43:18 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Read error: Connection reset by peer)
2025-07-31 17:42:36 +0200gorignak(~gorignak@user/gorignak) gorignak
2025-07-31 17:41:57 +0200chele(~chele@user/chele) (Remote host closed the connection)
2025-07-31 17:35:12 +0200ttybitnik(~ttybitnik@user/wolper) (Remote host closed the connection)
2025-07-31 17:34:29 +0200amadaluzia(~amadaluzi@user/amadaluzia) (Ping timeout: 240 seconds)
2025-07-31 17:33:52 +0200amadaluzia_(~amadaluzi@user/amadaluzia) amadaluzia
2025-07-31 17:29:42 +0200haritz(~hrtz@user/haritz) haritz
2025-07-31 17:29:42 +0200haritz(~hrtz@2a01:4b00:bc2e:7000:d5af:a266:ca31:5ef8) (Changing host)
2025-07-31 17:29:42 +0200haritz(~hrtz@2a01:4b00:bc2e:7000:d5af:a266:ca31:5ef8)
2025-07-31 17:29:37 +0200 <int-e> The main issue with SafeHaskell is that it captures a binary distinction, where safety is not breaking the type system (no unsafeCoerce or unsafePerformIO), so it's useless if you want other guarantees even if the inference mechanism would be the same (only controlling imports and exports); you'd have to redo the entire libary ecosystem to use that new safety notion.
2025-07-31 17:26:59 +0200d34db33f(~d34db33f@user/d34db33f) d34db33f
2025-07-31 17:26:45 +0200d34db33f(~d34db33f@user/d34db33f) (Ping timeout: 248 seconds)
2025-07-31 17:26:16 +0200 <int-e> (that trust is managed through ghc's -trust flag (and a few others) and also the `ghc-pkg trust` command)
2025-07-31 17:24:27 +0200 <int-e> (the user)
2025-07-31 17:24:24 +0200 <lambdabot> :)
2025-07-31 17:24:24 +0200 <int-e> @bot
2025-07-31 17:24:10 +0200 <int-e> eldritchcookie: Yes, I believe this is being deprecated, because it has like 1 user. But no, the module is still unsafe. However, if a Trustworthy module exported by a package that is *trusted* then that module can be imported into a Safe module.
2025-07-31 17:23:39 +0200tromp(~textual@2001:1c00:3487:1b00:b928:de3f:1dfd:983a) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-07-31 17:19:38 +0200 <__monty__> eldritchcookie: Not an answer but I think SafeHaskell is being deprecated?
2025-07-31 17:16:44 +0200caubert(~caubert@user/caubert) caubert
2025-07-31 17:16:20 +0200ubert(~Thunderbi@178.165.167.35.wireless.dyn.drei.com) ubert
2025-07-31 17:14:43 +0200 <sshine> Bowuigi: cool, thanks :)
2025-07-31 17:14:01 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) (Quit: WeeChat 4.5.2)
2025-07-31 17:10:44 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-07-31 17:09:14 +0200 <haskellbridge> <Bowuigi> sshine There's a ton of proposals on indentation-sensitive syntax, see: https://github.com/jumper149/haskeme or https://srfi.schemers.org/srfi-119/srfi-119.html (https://readable.sourceforge.io/) or https://srfi.schemers.org/srfi-110/srfi-110.html or https://srfi.schemers.org/srfi-49/srfi-49.html
2025-07-31 17:09:14 +0200 <haskellbridge> <eldritchcookie> if i have {-#LANGUAGE Trustyworthy#-} and i call ghc with -xSafe can i import unsafe modules?
2025-07-31 17:03:49 +0200caubert(~caubert@user/caubert) (Ping timeout: 248 seconds)
2025-07-31 17:01:44 +0200puke(~puke@user/puke) (Quit: puke)
2025-07-31 16:58:53 +0200caubert(~caubert@user/caubert) caubert
2025-07-31 16:57:51 +0200jespada(~jespada@r186-48-25-255.dialup.adsl.anteldata.net.uy) (Read error: Connection reset by peer)
2025-07-31 16:56:30 +0200d34db33f(~d34db33f@user/d34db33f) d34db33f
2025-07-31 16:49:41 +0200tabaqui1(~tabaqui@167.71.80.236) (Quit: WeeChat 4.5.1)
2025-07-31 16:49:22 +0200jmcantrell(~weechat@user/jmcantrell) jmcantrell
2025-07-31 16:46:43 +0200gorignak(~gorignak@user/gorignak) (Quit: quit)
2025-07-31 16:46:25 +0200caubert(~caubert@user/caubert) (Ping timeout: 276 seconds)
2025-07-31 16:44:59 +0200tromp(~textual@2001:1c00:3487:1b00:b928:de3f:1dfd:983a)
2025-07-31 16:43:16 +0200Digit(~user@user/digit) Digit
2025-07-31 16:41:33 +0200DigitDigitteknohippie
2025-07-31 16:37:46 +0200CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen
2025-07-31 16:36:33 +0200gorignak(~gorignak@user/gorignak) gorignak
2025-07-31 16:36:18 +0200gorignak(~gorignak@user/gorignak) (Quit: quit)
2025-07-31 16:31:48 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Read error: Connection reset by peer)
2025-07-31 16:29:26 +0200Sgeo(~Sgeo@user/sgeo) Sgeo
2025-07-31 16:26:09 +0200 <jreicher> But from a functional point of view, I still hesitate with Lisp. It's kind of nice that the homoiconicity brought first-class functions (accidentally?) to programmers, but by the same token it also brought unlimited mutability.
2025-07-31 16:23:53 +0200fp(~Thunderbi@2001:708:20:1406::10c5) (Ping timeout: 252 seconds)