2024/11/01

Newest at the top

2024-11-01 16:25:41 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2024-11-01 16:24:48 +0100rvalue(~rvalue@user/rvalue) rvalue
2024-11-01 16:24:16 +0100rvalue(~rvalue@user/rvalue) (Read error: Connection reset by peer)
2024-11-01 16:22:36 +0100econo_(uid147250@id-147250.tinside.irccloud.com)
2024-11-01 16:21:56 +0100AlexZenon(~alzenon@178.34.150.252)
2024-11-01 16:21:13 +0100ghoulguyglguy
2024-11-01 16:19:42 +0100ShelobShe
2024-11-01 16:16:09 +0100AlexZenon(~alzenon@178.34.150.252) (Ping timeout: 276 seconds)
2024-11-01 16:15:30 +0100morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 276 seconds)
2024-11-01 16:13:50 +0100misterfish(~misterfis@31-161-39-137.biz.kpn.net) (Ping timeout: 252 seconds)
2024-11-01 16:13:42 +0100CiaoSen(~Jura@2a05:5800:487:0:ca4b:d6ff:fec1:99da) CiaoSen
2024-11-01 16:12:17 +0100ash3en(~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en
2024-11-01 16:10:15 +0100morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-11-01 16:00:10 +0100k_hachig_(~k_hachig@2607:fea8:351d:ef0:901a:fefb:e87f:78b3) (Ping timeout: 272 seconds)
2024-11-01 15:53:31 +0100k_hachig_(~k_hachig@2607:fea8:351d:ef0:901a:fefb:e87f:78b3) k_hachig
2024-11-01 15:50:24 +0100tabemann(~tabemann@2600:1700:7990:24e0:141f:cdda:2f28:e1cc)
2024-11-01 15:50:04 +0100tabemann(~tabemann@2600:1700:7990:24e0:cb63:a13b:e8da:1b84) (Remote host closed the connection)
2024-11-01 15:46:43 +0100 <EvanR> whether it's formalized somewhere
2024-11-01 15:46:32 +0100 <EvanR> we choose when and what abstract world to live in
2024-11-01 15:45:55 +0100 <merijn> It just says "I will convert this to a pure value", and it's up to you to not do stupid shit
2024-11-01 15:45:08 +0100 <merijn> mauke: tbf, nothing about capi promises to obey the C standard ;)
2024-11-01 15:43:42 +0100 <mauke> merijn: the 'const volatile' thing can't be written by the program, but it may still change (memory-mapped timer or something)
2024-11-01 15:43:08 +0100 <EvanR> einstein forgot to put const
2024-11-01 15:42:54 +0100 <EvanR> now while c_pi doesn't change over time, some people still think c changes over time (c being the speed of light)
2024-11-01 15:42:29 +0100 <mauke> the presence of the initializer makes it a definition, and modifying an object whose definition includes 'const' is UB
2024-11-01 15:41:58 +0100 <mauke> EvanR: you're right, I misremembered
2024-11-01 15:40:31 +0100vgtw(~vgtw@user/vgtw) vgtw
2024-11-01 15:40:26 +0100 <EvanR> unless nothing means anything, which I guess is one way to look at things
2024-11-01 15:40:10 +0100 <EvanR> "const means nothing" is just false
2024-11-01 15:40:09 +0100 <merijn> (or on non-embedded I suppose)
2024-11-01 15:39:59 +0100 <merijn> mauke: Which of course in embedded doesn't prevent an address from changing in memory mapped IO
2024-11-01 15:39:34 +0100 <merijn> mauke: Pretty sure const *is* "modification = UB"
2024-11-01 15:39:26 +0100vgtw(~vgtw@user/vgtw) (Ping timeout: 255 seconds)
2024-11-01 15:39:21 +0100 <merijn> mauke: Sure, but you're not permitted to write to that
2024-11-01 15:39:05 +0100 <EvanR> you can say that values in haskell change over time
2024-11-01 15:38:29 +0100 <EvanR> but like, I can write to any object in haskell too
2024-11-01 15:38:22 +0100 <mauke> I know 'const volatile foo' is explicitly permmitted
2024-11-01 15:38:14 +0100 <EvanR> sure
2024-11-01 15:38:12 +0100 <mauke> hold on, I need to check my standards
2024-11-01 15:38:08 +0100 <merijn> EvanR: C programmers regularly break everything :p
2024-11-01 15:37:49 +0100 <EvanR> unless you break everything, which you can do in haskell also
2024-11-01 15:37:33 +0100 <EvanR> in C, that's a const double, it's not changing
2024-11-01 15:37:31 +0100 <merijn> mauke: because modifying pi is UB
2024-11-01 15:37:18 +0100 <merijn> mauke: tbf, it's actually sound
2024-11-01 15:37:18 +0100 <mauke> const means read-only, not constant
2024-11-01 15:37:10 +0100 <merijn> EvanR: Because const means nothing
2024-11-01 15:37:03 +0100 <EvanR> how does const double pi change over time
2024-11-01 15:36:30 +0100 <mauke> but that's unsound, since the value of pi can change over time
2024-11-01 15:36:18 +0100 <mauke> is documented as letting you refer to const double pi = 3.14;
2024-11-01 15:36:01 +0100 <mauke> huh. foreign import capi "pi.h value pi" c_pi :: CDouble