2025/07/24

Newest at the top

2025-07-24 22:07:05 +0200caubert(~caubert@user/caubert) caubert
2025-07-24 22:05:09 +0200caubert(~caubert@user/caubert) (Ping timeout: 248 seconds)
2025-07-24 22:04:22 +0200 <__monty__> sm: I could try but wouldn't the executable be `shake`?
2025-07-24 22:02:33 +0200 <__monty__> dminuoso: For now it's internal.
2025-07-24 22:00:28 +0200caubert(~caubert@user/caubert) caubert
2025-07-24 22:00:14 +0200jespada(~jespada@2800:a4:2291:9400:bcdf:5144:5f9c:bc05) jespada
2025-07-24 21:59:13 +0200jespada(~jespada@2800:a4:2291:9400:1dfb:720c:e8a8:5a0a) (Ping timeout: 248 seconds)
2025-07-24 21:54:09 +0200CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen
2025-07-24 21:51:40 +0200caubert(~caubert@user/caubert) (Ping timeout: 252 seconds)
2025-07-24 21:47:08 +0200caubert(~caubert@user/caubert) caubert
2025-07-24 21:43:13 +0200 <glguy> Cool!
2025-07-24 21:43:01 +0200 <glguy> Since: base-4.18.0.0
2025-07-24 21:42:05 +0200 <glguy> Oh, when did base get that?
2025-07-24 21:41:41 +0200 <dolio> I guess there is Foreign.C.ConstPtr. Maybe that can do it?
2025-07-24 21:40:26 +0200 <dolio> They all look like they're happening in auto-generated FFI files, so if there isn't some way to modify the FFI signature to make it generate a different signature, there's probably nothing you can do.
2025-07-24 21:39:45 +0200 <dolio> Okay, yeah, it's probably that.
2025-07-24 21:39:31 +0200 <glguy> Oh, ok. Last I'd looked GHC 's capi just wasn't written knowing C had qualifiers
2025-07-24 21:38:16 +0200 <dolio> glguy: They all appear to be "return discards a 'const' qualifier" warnings.
2025-07-24 21:36:18 +0200 <glguy> dolio: could you share the warnings? I want to see if it's worth setting up an environment that reproduces them to then fix them
2025-07-24 21:34:28 +0200caubert(~caubert@user/caubert) (Ping timeout: 240 seconds)
2025-07-24 21:33:17 +0200trickard_(~trickard@cpe-62-98-47-163.wireline.com.au)
2025-07-24 21:33:03 +0200trickard(~trickard@cpe-62-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-07-24 21:30:02 +0200gorignak(~gorignak@user/gorignak) (Quit: quit)
2025-07-24 21:28:27 +0200chele(~chele@user/chele) (Remote host closed the connection)
2025-07-24 21:25:40 +0200LainIwakura(~LainIwaku@user/LainIwakura) LainIwakura
2025-07-24 21:23:14 +0200jespada(~jespada@2800:a4:2291:9400:1dfb:720c:e8a8:5a0a) jespada
2025-07-24 21:21:00 +0200Guest96(~Guest96@81-207-104-14.fixed.kpn.net) (Client Quit)
2025-07-24 21:20:51 +0200 <geekosaur> and let's not even think about wrapper scripts
2025-07-24 21:20:42 +0200 <geekosaur> doing it right is tricky: (a) sometimes you don't get a path, especially on non-Unix, so you have to do a PATH search yourself and fail if it wasn't on the path (b) it may be a symlink to the real program, so you may need to resolve those (good luck if it's Windows!)
2025-07-24 21:20:19 +0200Guest96(~Guest96@81-207-104-14.fixed.kpn.net)
2025-07-24 21:17:16 +0200caubert(~caubert@user/caubert) caubert
2025-07-24 21:16:39 +0200LainIwakura(~LainIwaku@user/LainIwakura) (Quit: Client closed)
2025-07-24 21:15:56 +0200 <sm> https://hackage.haskell.org/package/base-4.21.0.0/docs/System-Environment.html#v:getExecutablePath or something
2025-07-24 21:13:29 +0200 <sm> can you use the standard tricks shell scripts use to find their file location ? Analyse the command line, etc ?
2025-07-24 21:12:28 +0200vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 240 seconds)
2025-07-24 21:11:46 +0200sord937(~sord937@gateway/tor-sasl/sord937) (Quit: sord937)
2025-07-24 21:09:19 +0200manwithluck(~manwithlu@2a09:bac1:5bc0:20::39b:8b) manwithluck
2025-07-24 21:09:08 +0200sprotte24(~sprotte24@p200300d16f056400b9509f58729e6016.dip0.t-ipconnect.de)
2025-07-24 21:08:34 +0200manwithluck(~manwithlu@2a09:bac1:5bc0:20::39b:8b) (Ping timeout: 260 seconds)
2025-07-24 21:04:37 +0200fp(~Thunderbi@89-27-10-140.bb.dnainternet.fi) fp
2025-07-24 21:04:13 +0200 <dminuoso> __monty__: Is this some internal work tool or something you want to share publically?
2025-07-24 21:03:51 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2025-07-24 21:00:44 +0200caconym74(~caconym@user/caconym) caconym
2025-07-24 21:00:03 +0200caconym74(~caconym@user/caconym) (Quit: bye)
2025-07-24 20:57:46 +0200caubert(~caubert@user/caubert) (Ping timeout: 276 seconds)
2025-07-24 20:56:27 +0200rvalue-rvalue
2025-07-24 20:55:39 +0200LainIwakura(~LainIwaku@user/LainIwakura) LainIwakura
2025-07-24 20:53:13 +0200jespada(~jespada@2800:a4:2291:9400:14c2:89da:d45:6f6a) (Ping timeout: 276 seconds)
2025-07-24 20:52:36 +0200 <__monty__> sm: While that technically works I'm looking for a less chaotic method, it's already a lot of juggling of formats and templates.
2025-07-24 20:52:29 +0200rvalue(~rvalue@about/hackers/rvalue) (Ping timeout: 240 seconds)