2025/03/22

Newest at the top

2025-03-22 20:11:59 +0100lxsameer(~lxsameer@Serene/lxsameer) (Ping timeout: 260 seconds)
2025-03-22 20:11:38 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-03-22 20:07:54 +0100hattckory(~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) (Ping timeout: 260 seconds)
2025-03-22 20:06:43 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-22 20:03:47 +0100dtman34(~dtman34@2601:447:d000:1f5e:46df:8e62:8caf:e6f6) dtman34
2025-03-22 20:02:39 +0100dtman34(~dtman34@c-75-72-179-251.hsd1.mn.comcast.net) (Ping timeout: 260 seconds)
2025-03-22 20:00:45 +0100caconym(~caconym@user/caconym) caconym
2025-03-22 20:00:15 +0100yago(~yago@2a0c:5a82:1708:200:5441:db13:8b84:88e5) (Ping timeout: 276 seconds)
2025-03-22 20:00:01 +0100caconym(~caconym@user/caconym) (Quit: bye)
2025-03-22 19:57:59 +0100 <geekosaur> ghc just looks for an already-built package. if you use an external interpreter, it would need to tell the remote `ghc-iserv`, which may already be running, to load the plugin from its package store and restart
2025-03-22 19:56:37 +0100 <geekosaur> ghc doesn't compile them, your build tool does. (for example I think cabal has you list them as `build-tool-dependency` so they're built before ghc requires them)
2025-03-22 19:56:14 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-03-22 19:55:56 +0100dtman34(~dtman34@c-75-72-179-251.hsd1.mn.comcast.net) dtman34
2025-03-22 19:55:14 +0100dtman34(~dtman34@2601:447:d000:1f5e:adb1:5444:1e59:864f) (Ping timeout: 248 seconds)
2025-03-22 19:54:26 +0100rvalue-rvalue
2025-03-22 19:52:59 +0100 <Noinia> i.e. if one can compile, and therefore run, more or less arbitrary haskell code, within WASM [*], I don't really see what the issue should be. (Provided that those plugins don't e.g. try to access files/or do stuff inherently restricted by the wasm runtime)
2025-03-22 19:51:02 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-22 19:50:55 +0100 <Noinia> why is it a binary plugin? I.e. the ghc plugins are also just packages that it compiles no?
2025-03-22 19:49:21 +0100 <geekosaur> or otherwise arranges for the external interpreter to have it available?
2025-03-22 19:48:55 +0100 <geekosaur> it's not subtle at all: who or what translates a binary plugin to a different architecture (including JS or wasm)?
2025-03-22 19:48:54 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-03-22 19:48:43 +0100 <Noinia> but I guess it means it will be a while before I can start using the WASM backend in my project :(
2025-03-22 19:48:20 +0100 <Noinia> hmm, I don't think I fully understand all the subtleties
2025-03-22 19:48:10 +0100rvalue(~rvalue@user/rvalue) (Ping timeout: 252 seconds)
2025-03-22 19:48:04 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 260 seconds)
2025-03-22 19:47:54 +0100rvalue-(~rvalue@user/rvalue) rvalue
2025-03-22 19:47:17 +0100 <geekosaur> the problem being that you can't arrange for the plugin to run in the external interpreter, especially if it's wrapped in some node glue
2025-03-22 19:44:47 +0100 <geekosaur> so plugins are most likely unimplemented
2025-03-22 19:44:33 +0100 <geekosaur> I think wasm always forces external interpreter?
2025-03-22 19:43:22 +0100 <Noinia> I don't see a ticket on gitlab, but compiling my package (which uses both TH and a GHC plugin) fails with 'Plugins require -fno-external-interpreter'. (But adding that flag does not really seem to make any difference for some reason)
2025-03-22 19:43:20 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-03-22 19:42:19 +0100 <Noinia> Does anyone know if the wasm backend is suposed to support ghc-plugins (together with TH?) already?
2025-03-22 19:42:13 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-22 19:41:13 +0100hgolden(~hgolden@2603:8000:9d00:3ed1:6ff3:8389:b901:6363) hgolden
2025-03-22 19:35:44 +0100hgolden_(~hgolden@2603:8000:9d00:3ed1:6ff3:8389:b901:6363) (Remote host closed the connection)
2025-03-22 19:33:29 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-03-22 19:31:32 +0100JuanDaugherty(~juan@user/JuanDaugherty) (Quit: praxis.meansofproduction.biz (juan@acm.org))
2025-03-22 19:28:34 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-22 19:24:40 +0100Square(~Square@user/square) Square
2025-03-22 19:24:24 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-03-22 19:21:10 +0100EvanR(~EvanR@user/evanr) EvanR
2025-03-22 19:20:50 +0100EvanR(~EvanR@user/evanr) (Remote host closed the connection)
2025-03-22 19:20:28 +0100Cattycatties
2025-03-22 19:18:23 +0100ash3en(~Thunderbi@89.56.182.235) ash3en
2025-03-22 19:17:44 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-03-22 19:13:04 +0100ash3en(~Thunderbi@89.56.182.235) (Quit: ash3en)
2025-03-22 19:12:49 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-22 19:09:27 +0100DigitteknohippieDigit
2025-03-22 19:02:34 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 260 seconds)
2025-03-22 19:01:59 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)