2025/09/29

Newest at the top

2025-09-29 14:53:55 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 255 seconds)
2025-09-29 14:51:14 +0200ThePenguin(~ThePengui@cust-95-80-28-221.csbnet.se) ThePenguin
2025-09-29 14:51:01 +0200 <yin> ncf oh that's nice
2025-09-29 14:50:14 +0200 <yin> i don't know
2025-09-29 14:50:11 +0200 <yin> or rather (pure a)?
2025-09-29 14:49:26 +0200 <yin> a <f> b = f <$> a <*> b
2025-09-29 14:49:22 +0200ThePenguin(~ThePengui@cust-95-80-28-221.csbnet.se) (Remote host closed the connection)
2025-09-29 14:49:17 +0200 <ncf> well, i'm talking about the notation mcbride came up with, not that weird typeclass encoding. agda has this: https://agda.readthedocs.io/en/stable/language/syntactic-sugar.html#idiom-brackets
2025-09-29 14:48:51 +0200 <yin> i want
2025-09-29 14:48:49 +0200 <yin> not quite
2025-09-29 14:48:31 +0200arandombit(~arandombi@user/arandombit) (Ping timeout: 255 seconds)
2025-09-29 14:47:18 +0200 <yin> ncf: wait are you talking about this? https://wiki.haskell.org/Idiom_brackets
2025-09-29 14:43:12 +0200phm(~peter@user/phm) phm
2025-09-29 14:42:45 +0200 <yin> ncf: yes
2025-09-29 14:42:38 +0200 <ncf> you just want idiom brackets
2025-09-29 14:42:25 +0200 <yin> s/no/now
2025-09-29 14:42:20 +0200 <yin> no have <f> mean (lift f)
2025-09-29 14:42:03 +0200 <yin> lift f a b = liftA2 f (pure a) b
2025-09-29 14:41:37 +0200 <yin> ok listen up
2025-09-29 14:40:49 +0200 <ncf> (<*>) = liftA2 ($); (<$>) = liftA1
2025-09-29 14:40:02 +0200 <ncf> just don't do that with ($) or (*) and you'll be fine :)
2025-09-29 14:38:39 +0200craunts79(~craunts@136.158.7.194)
2025-09-29 14:37:13 +0200xdej(~xdej@quatramaran.salle-s.org) xdej
2025-09-29 14:35:24 +0200mulk(~mulk@pd95144c3.dip0.t-ipconnect.de) (Ping timeout: 244 seconds)
2025-09-29 14:32:15 +0200 <[exa]> yin: btw in my code I usually do this with shortcuts like (<+>) = liftA2 (+). Most frequently with <:> I'd say.
2025-09-29 14:29:48 +0200 <yin> probie: i like it. i agree with you though, for some definition of "hard to read"
2025-09-29 14:26:13 +0200trickard_(~trickard@cpe-50-98-47-163.wireline.com.au)
2025-09-29 14:26:00 +0200trickard(~trickard@cpe-50-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-09-29 14:17:51 +0200 <[exa]> yin: ah okay
2025-09-29 14:17:33 +0200APic(apic@chiptune.apic.name) APic
2025-09-29 14:11:34 +0200APic(apic@apic.name) (Ping timeout: 260 seconds)
2025-09-29 14:10:48 +0200lisq(~quassel@lis.moe) lisq
2025-09-29 14:08:51 +0200 <yahb2> liftA2 @((->) _) ; :: Applicative ((->) w) => ; (a -> b -> c) -> (w -> a) -> (w -> b) -> w -> c
2025-09-29 14:08:50 +0200 <probie> % :t liftA2 @((->) _)
2025-09-29 14:08:15 +0200 <yin> I never know how to do this here
2025-09-29 14:07:33 +0200 <yahb2> <interactive>:19:1: error: [GHC-39999] ; • No instance for ‘Show ; ((a0 -> b0 -> c0) -> (w0 -> a0) -> (w0 -> b0) -> w0 -> c0)’ ; arising from a use of ‘Yahb2Def...
2025-09-29 14:07:33 +0200 <yin> % liftA2 @((->) _)
2025-09-29 14:07:25 +0200 <probie> yin: Is it that great? It works because verbs and nouns are distinct, and long trains are pretty hard to read
2025-09-29 14:06:59 +0200 <yin> [exa]: liftA2 implementation can be more performant for some Applicatives
2025-09-29 14:06:31 +0200 <yin> hmm
2025-09-29 14:06:18 +0200 <lambdabot> error: parse error on input ‘->’
2025-09-29 14:06:17 +0200 <yin> :t liftA2 @((->) _)
2025-09-29 14:06:03 +0200 <[exa]> yin: what's wrong with (+) <$> Just 1 <*> Just 2 ?
2025-09-29 14:05:20 +0200 <yin> in the language J, (h f g) is (liftA2 f h g), a "monadic fork" they call it, as a basic syntax feature, which is GREAT
2025-09-29 13:59:56 +0200 <[exa]> as in, it's not gonna be a pattern without some extra work, but you can stash it somewhere in guards: | Just arg <- preview (prefixed "hahaha") arg = ...
2025-09-29 13:56:28 +0200 <[exa]> chromoblob: you can do that pretty well with prisms
2025-09-29 13:56:01 +0200 <chromoblob> i also want pattern syntax ("abc" ++ s) - like n+k patterns, but for strings
2025-09-29 13:55:50 +0200 <yin> [exa]: at least that wouldn't trip markdown up
2025-09-29 13:55:10 +0200divlamir(~divlamir@user/divlamir) divlamir
2025-09-29 13:55:08 +0200[exa]wishes for back-backtick, the foretick, like ´ but worse