2026/04/29

Newest at the top

2026-04-29 23:10:46 +0000 <EvanR> sort of a default implementation concept
2026-04-29 23:10:35 +0000 <EvanR> *ponders what you really want out of the specialization of Eq example*
2026-04-29 23:09:42 +0000arandombit(~arandombi@user/arandombit) (Remote host closed the connection)
2026-04-29 23:08:16 +0000 <EvanR> kind of like, immutable data is great, but then go mutate the data anyway
2026-04-29 23:07:48 +0000 <EvanR> yeah if you want to ignore the "no overlapping" rule of type classes, then you might be losing some of the goodness of type classes
2026-04-29 23:07:06 +0000layline_(~layline@149.154.26.170) layline
2026-04-29 23:06:11 +0000m_a_r_k(~m_a_r_k@archlinux/support/mark) m_a_r_k
2026-04-29 23:04:22 +0000 <geekosaur> the ghc users manual has an explanation of how instances are picked in that case
2026-04-29 23:01:17 +0000bitdex(~bitdex@gateway/tor-sasl/bitdex) bitdex
2026-04-29 22:59:21 +0000 <hadronized> but never really thought about how it works behind the hood
2026-04-29 22:59:12 +0000 <hadronized> I guess it’s OverlappingInstances
2026-04-29 22:58:42 +0000 <hadronized> if Stuff Int is provided, then what to pick?
2026-04-29 22:58:29 +0000 <hadronized> instance Eq Int where …
2026-04-29 22:58:21 +0000 <hadronized> instance Stuff a => Eq a where …
2026-04-29 22:57:27 +0000 <EvanR> what do you mean by specialization
2026-04-29 22:57:04 +0000 <hadronized> but I would also like to have specialization, and coherence makes it pretty hard to think about
2026-04-29 22:56:49 +0000 <hadronized> I’ve been designing a language lately and just assumed I’d use a typeclass kind of abstraction
2026-04-29 22:56:47 +0000humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-04-29 22:56:22 +0000 <EvanR> problem? points at Typeclasses vs The World
2026-04-29 22:55:57 +0000 <EvanR> eyebrow raises
2026-04-29 22:55:49 +0000Fischmiep(~Fischmiep@user/Fischmiep) Fischmiep
2026-04-29 22:55:42 +0000 <hadronized> (overlapping instances, specialization, etc.)
2026-04-29 22:55:36 +0000 <hadronized> I wonder whether there are other approaches, especially dodging all the coherence problems
2026-04-29 22:54:59 +0000 <EvanR> hadronized, historically, so that we can use the + operator on more than just Int... or Int and Float... or some other ad hoc thing
2026-04-29 22:54:03 +0000Pozyomka(~pyon@user/pyon) (Quit: WeeChat 4.9.0)
2026-04-29 22:53:25 +0000Fischmiep(~Fischmiep@user/Fischmiep) (Client Quit)
2026-04-29 22:50:31 +0000Fischmiep(~Fischmiep@user/Fischmiep) Fischmiep
2026-04-29 22:50:29 +0000arahael(~wetfoot@user/arahael) (Quit: WeeChat 4.6.3)
2026-04-29 22:50:00 +0000Fischmiep(~Fischmiep@user/Fischmiep) (Read error: Connection reset by peer)
2026-04-29 22:46:26 +0000peterbecich(~Thunderbi@71.84.33.135) peterbecich
2026-04-29 22:45:35 +0000FallenSky(~FallenSky@user/FallenSky) FallenSky
2026-04-29 22:40:24 +0000Pozyomka(~pyon@user/pyon) pyon
2026-04-29 22:38:14 +0000Square(~Square4@user/square) (Ping timeout: 245 seconds)
2026-04-29 22:38:06 +0000tremon(~tremon@83.80.159.219) (Quit: getting boxed in)
2026-04-29 22:38:03 +0000ChaiTRex(~ChaiTRex@user/chaitrex) (Quit: ChaiTRex)
2026-04-29 22:38:00 +0000divlamir(~divlamir@user/divlamir) divlamir
2026-04-29 22:35:36 +0000Square2(~Square@user/square) Square
2026-04-29 22:24:45 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2026-04-29 22:23:30 +0000divlamir(~divlamir@user/divlamir) (Ping timeout: 245 seconds)
2026-04-29 22:18:13 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-29 22:17:47 +0000Sgeo(~Sgeo@user/sgeo) Sgeo
2026-04-29 22:16:50 +0000YuutaW(~YuutaW@infornography.yta.moe) (Ping timeout: 248 seconds)
2026-04-29 22:16:37 +0000divlamir(~divlamir@user/divlamir) divlamir
2026-04-29 22:16:19 +0000yuuta(~YuutaW@infornography.yta.moe) YuutaW
2026-04-29 22:15:28 +0000__monty__(~toonn@user/toonn) (Quit: leaving)
2026-04-29 22:14:28 +0000divlamir(~divlamir@user/divlamir) (Ping timeout: 276 seconds)
2026-04-29 22:14:06 +0000misterfish(~misterfis@84.53.85.146) (Ping timeout: 244 seconds)
2026-04-29 22:12:50 +0000layline_(~layline@149.154.26.170) (Ping timeout: 252 seconds)
2026-04-29 22:06:58 +0000divlamir_divlamir
2026-04-29 22:06:34 +0000divlamir(~divlamir@user/divlamir) (Ping timeout: 245 seconds)