Newest at the top
| 2025-02-12 19:11:22 +0100 | jespada | (~jespada@2800:a4:22f4:ae00:fc16:e598:5958:94e6) (Quit: My Mac has gone to sleep. ZZZzzz…) |
| 2025-02-12 19:11:10 +0100 | Googulator | (~Googulato@2a01-036d-0106-4074-f40d-d825-16f5-119a.pool6.digikabel.hu) (Ping timeout: 240 seconds) |
| 2025-02-12 19:10:27 +0100 | tri | (~tri@ool-44c70bcb.dyn.optonline.net) |
| 2025-02-12 19:07:37 +0100 | Googulator97 | (~Googulato@2a01-036d-0106-4074-f40d-d825-16f5-119a.pool6.digikabel.hu) |
| 2025-02-12 19:04:20 +0100 | lxsameer | (lxsameer@Serene/lxsameer) lxsameer |
| 2025-02-12 19:02:34 +0100 | lxsameer | (~lxsameer@Serene/lxsameer) (Ping timeout: 260 seconds) |
| 2025-02-12 19:01:20 +0100 | [tank] | (~tank@213.18.138.85) |
| 2025-02-12 19:01:11 +0100 | rawles | (~rawles@user/rawles) (WeeChat 3.8) |
| 2025-02-12 18:59:20 +0100 | <hololeap> | does anyone know of a library that has this functionality? (removing ANSI escape sequences from a ByteString (or Text)) |
| 2025-02-12 18:58:19 +0100 | zungi | (~tory@user/andrewchawk) andrewchawk |
| 2025-02-12 18:53:21 +0100 | zungi | (~tory@user/andrewchawk) (Quit: "Moving to other building...") |
| 2025-02-12 18:52:59 +0100 | <hololeap> | weird. this works in 9.4 but in 9.8 it just causes my exe to spin forever: https://stackoverflow.com/a/41055988 |
| 2025-02-12 18:51:54 +0100 | Smiles | (uid551636@id-551636.lymington.irccloud.com) (Quit: Connection closed for inactivity) |
| 2025-02-12 18:48:51 +0100 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) |
| 2025-02-12 18:47:50 +0100 | sord937 | (~sord937@gateway/tor-sasl/sord937) (Quit: sord937) |
| 2025-02-12 18:47:22 +0100 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2025-02-12 18:46:14 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 260 seconds) |
| 2025-02-12 18:44:38 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2025-02-12 18:41:53 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-02-12 18:36:02 +0100 | byorgey | (~byorgey@user/byorgey) byorgey |
| 2025-02-12 18:36:02 +0100 | byorgey | (~byorgey@155.138.238.211) (Changing host) |
| 2025-02-12 18:36:02 +0100 | byorgey | (~byorgey@155.138.238.211) |
| 2025-02-12 18:35:47 +0100 | <geekosaur> | I still think the Report is the wrong place for it, implementations should be able to make their own decisions. ghc is kinda wrong in deferring it to library docs instead of compiler docs though |
| 2025-02-12 18:33:30 +0100 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) |
| 2025-02-12 18:31:50 +0100 | haritz | (~hrtz@user/haritz) haritz |
| 2025-02-12 18:31:50 +0100 | haritz | (~hrtz@2a02:8010:65b5:0:5d9a:9bab:ee5e:b737) (Changing host) |
| 2025-02-12 18:31:48 +0100 | haritz | (~hrtz@2a02:8010:65b5:0:5d9a:9bab:ee5e:b737) |
| 2025-02-12 18:31:31 +0100 | <monochrom> | Hey, vote for me to be the absolute monarch, then I will make it happen! >:) |
| 2025-02-12 18:31:24 +0100 | <EvanR> | that provides an authoritative answer to my question |
| 2025-02-12 18:30:49 +0100 | <monochrom> | So basically the Report bitrots and all the clarifications happen in library docs instead. |
| 2025-02-12 18:30:31 +0100 | JuanDaugherty | (~juan@user/JuanDaugherty) (Exeunt DS Producers) |
| 2025-02-12 18:30:13 +0100 | <EvanR> | that is almost the latest version of unicode being linked too |
| 2025-02-12 18:30:09 +0100 | <monochrom> | It would have been entered into a new version of the Report, if only people bothered to form a committee for it. |
| 2025-02-12 18:29:24 +0100 | <geekosaur> | "The character type Char represents Unicode codespace and its elements are code points as in definitions D9 and D10 of the Unicode Standard." |
| 2025-02-12 18:29:14 +0100 | <monochrom> | \∩/ |
| 2025-02-12 18:28:47 +0100 | <geekosaur> | oh, I found it. even though it's necessarily a compiler built-in, it's specified in library documentation https://downloads.haskell.org/ghc/latest/docs/libraries/base-4.21.0.0-8e62/Data-Char.html#t:Char |
| 2025-02-12 18:28:19 +0100 | <EvanR> | practically it seems to be in one to one correspondence with integers in the precise range of unicode's... codes |
| 2025-02-12 18:27:37 +0100 | <geekosaur> | (which is a shocking amount once you start digging into it…) |
| 2025-02-12 18:27:35 +0100 | <monochrom> | I don't have absolute certainty that Char = codepoint, but I use that as a working theory and it works pretty well. |
| 2025-02-12 18:27:22 +0100 | <geekosaur> | but then you have to understand all the stuff the Report didn't specify |
| 2025-02-12 18:27:10 +0100 | <EvanR> | turns out once you understand what (latest) unicode is, Char makes less sense xD |
| 2025-02-12 18:26:55 +0100 | Wygulmage | (~Wygulmage@user/Wygulmage) (Quit: Client closed) |
| 2025-02-12 18:26:46 +0100 | <monochrom> | To understand what Char is, first you have to understand what Unicode is. >:) |
| 2025-02-12 18:26:38 +0100 | <EvanR> | which is how C considers characters |
| 2025-02-12 18:26:32 +0100 | saimazoon | (~hrtz@user/haritz) (Ping timeout: 252 seconds) |
| 2025-02-12 18:26:08 +0100 | <EvanR> | which is an integer, or codepoint. So "a fancy integer" seems yeah |
| 2025-02-12 18:25:42 +0100 | <EvanR> | like fffe |
| 2025-02-12 18:25:16 +0100 | <EvanR> | are literally not characters |
| 2025-02-12 18:25:01 +0100 | <EvanR> | and other non-characters |
| 2025-02-12 18:22:44 +0100 | <geekosaur> | but, strictly speaking, is wrong because surrogates are not characters |