2025/01/10

Newest at the top

2025-01-10 13:33:21 +0100 <hellwolf> the achilles' heel of of thesis project
2025-01-10 13:33:12 +0100 <mreh> before I delve into the literature, does anyone know if StableName equality is guaranteed when called on the same constructor? i.e. if I evaluate an object to WNHF will it always have the same StableName returned by makeStableName?
2025-01-10 13:31:37 +0100l_k(~student@85.172.76.97)
2025-01-10 13:31:19 +0100l_k(~student@81.177.127.117) (Ping timeout: 264 seconds)
2025-01-10 13:30:44 +0100mreh(~matthew@host86-146-25-121.range86-146.btcentralplus.com) mreh
2025-01-10 13:28:18 +0100l__k(~student@85.172.77.123)
2025-01-10 13:26:40 +0100l__k(~student@85.172.110.137) (Ping timeout: 244 seconds)
2025-01-10 13:26:26 +0100 <geekosaur> thesis project
2025-01-10 13:26:21 +0100 <geekosaur> yes
2025-01-10 13:25:15 +0100 <merijn> I think it was ezyang's baby?
2025-01-10 13:24:22 +0100 <hellwolf> I have watched a talk about backpack, awhile back. But I also heard that people behind backpack left.
2025-01-10 13:23:55 +0100l_k(~student@81.177.127.117)
2025-01-10 13:23:54 +0100 <merijn> they're part of backpack, yeah
2025-01-10 13:23:11 +0100 <hellwolf> I used mixins from cabal, if that's the same thing
2025-01-10 13:22:55 +0100 <merijn> And did you look at backpack?
2025-01-10 13:22:39 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2025-01-10 13:22:27 +0100 <merijn> But people already complain about binary sizes :p
2025-01-10 13:22:10 +0100 <merijn> hellwolf: monomorphising everything is (conceptually and theoretically) trivial
2025-01-10 13:21:57 +0100tomboy64(~tomboy64@user/tomboy64) tomboy64
2025-01-10 13:21:24 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-01-10 13:20:11 +0100vpan(~vpan@212.117.1.172) (Quit: Leaving.)
2025-01-10 13:18:47 +0100 <mari47944> huh i think there are a few proposals aligned, but i might be wrong
2025-01-10 13:18:24 +0100l_k(~student@217.107.126.75) (Ping timeout: 244 seconds)
2025-01-10 13:17:58 +0100 <hellwolf> no theory needed
2025-01-10 13:17:53 +0100 <hellwolf> CPP people just simply #define A TO_BE_B
2025-01-10 13:17:24 +0100 <hellwolf> It must be very complicated, theory wise :p
2025-01-10 13:17:12 +0100 <hellwolf> Type theory people will laugh at our enthusiasm.
2025-01-10 13:15:57 +0100l_k_(~student@85.172.110.63) (Ping timeout: 246 seconds)
2025-01-10 13:14:36 +0100l__k(~student@85.172.110.137)
2025-01-10 13:13:01 +0100l_k(~student@217.107.126.75)
2025-01-10 13:12:44 +0100l_k(~student@85.172.110.73) (Ping timeout: 264 seconds)
2025-01-10 13:10:46 +0100l__k(~student@217.107.126.148) (Ping timeout: 252 seconds)
2025-01-10 13:10:04 +0100 <[exa]> module-level forall, module monomorphization, yay, gogogo!
2025-01-10 13:09:38 +0100 <hellwolf> so there is room just to change how things are built
2025-01-10 13:09:31 +0100 <hellwolf> we don't usually distribute libraries binary form
2025-01-10 13:09:23 +0100 <hellwolf> perhaps just a different build mechanism
2025-01-10 13:09:01 +0100 <mari47944> hm not sure whether that feature requires a different module system or a different binary interface or both
2025-01-10 13:08:41 +0100l_k_(~student@85.172.110.63)
2025-01-10 13:08:18 +0100 <hellwolf> some referred to it as ML module maybe
2025-01-10 13:08:18 +0100 <[exa]> ah, the backpacky stuff
2025-01-10 13:08:06 +0100 <hellwolf> there is a specific name to it
2025-01-10 13:08:02 +0100 <hellwolf> I think people wanted a module where you can swap implementations after distribution
2025-01-10 13:07:55 +0100 <[exa]> heretics!
2025-01-10 13:07:51 +0100l_k(~student@85.172.110.73)
2025-01-10 13:07:48 +0100 <mari47944> many consider it improvable
2025-01-10 13:07:20 +0100 <[exa]> hellwolf: "module system" we don't have one?
2025-01-10 13:03:49 +0100 <hellwolf> nevermind.
2025-01-10 13:03:31 +0100 <hellwolf> hmm, no, even with orphaned instance you can't swap it out later, since compiling the library would require such type class exist.
2025-01-10 13:01:41 +0100 <hellwolf> Am I crazy to envision that type class and type families (perhaps type family fundeps) too could achieve the module system that we deserve? Though, perhaps packaging around it would be needed to make it more close to module system, instead of boilerplated type classes.
2025-01-10 12:57:23 +0100 <mari47944> i mean swapping technically fits into "fearless refactoring" ^^