Newest at the top
| 2025-03-11 17:57:10 +0100 | ft | (~ft@p508db291.dip0.t-ipconnect.de) ft |
| 2025-03-11 17:56:17 +0100 | alp_ | (~alp@2001:861:8ca0:4940:c565:4978:5e35:fdfc) |
| 2025-03-11 17:56:03 +0100 | shr\ke | (~shrike@user/shrke:31298) (Ping timeout: 265 seconds) |
| 2025-03-11 17:55:57 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 244 seconds) |
| 2025-03-11 17:54:29 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 260 seconds) |
| 2025-03-11 17:46:51 +0100 | jespada | (~jespada@2800:a4:235f:7f00:3596:12c9:751d:6561) jespada |
| 2025-03-11 17:44:31 +0100 | jespada | (~jespada@2800:a4:235f:7f00:3596:12c9:751d:6561) (Quit: My Mac has gone to sleep. ZZZzzz…) |
| 2025-03-11 17:38:30 +0100 | zungi | (~tory@user/andrewchawk) andrewchawk |
| 2025-03-11 17:37:21 +0100 | Smiles | (uid551636@id-551636.lymington.irccloud.com) (Quit: Connection closed for inactivity) |
| 2025-03-11 17:37:19 +0100 | euouae | (~euouae@user/euouae) (Ping timeout: 268 seconds) |
| 2025-03-11 17:34:01 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2025-03-11 17:33:05 +0100 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh |
| 2025-03-11 17:32:36 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 252 seconds) |
| 2025-03-11 17:28:12 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-11 17:27:48 +0100 | zungi | (~tory@user/andrewchawk) (Ping timeout: 264 seconds) |
| 2025-03-11 17:24:22 +0100 | izzyfalco | (~jake_pers@user/izzyfalco) (Ping timeout: 268 seconds) |
| 2025-03-11 17:17:59 +0100 | <tomsmeding> | or RULES, or ... |
| 2025-03-11 17:17:21 +0100 | <tomsmeding> | monochrom: can't generate import declarations from TH |
| 2025-03-11 17:17:05 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
| 2025-03-11 17:14:27 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Read error: Connection timed out) |
| 2025-03-11 17:13:37 +0100 | puke | (~puke@user/puke) (Quit: puke) |
| 2025-03-11 17:13:09 +0100 | acidjnk_new | (~acidjnk@p200300d6e7283f28c0a9d5fbe208cdcd.dip0.t-ipconnect.de) (Ping timeout: 248 seconds) |
| 2025-03-11 17:09:52 +0100 | pavonia | (~user@user/siracusa) (Quit: Bye!) |
| 2025-03-11 17:04:56 +0100 | izzyfalco | (~jake_pers@user/izzyfalco) izzyfalco |
| 2025-03-11 16:58:01 +0100 | <monochrom> | (Sorry I had too little sleep and too much coffee!) |
| 2025-03-11 16:57:18 +0100 | <monochrom> | This is known as the Monochrom Normal Form Theorem. |
| 2025-03-11 16:56:56 +0100 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 252 seconds) |
| 2025-03-11 16:56:44 +0100 | <monochrom> | Next mad scientist idea: While we can't eliminate CPP from Haskell, we can minimize it down to using CPP to set just a few boolean/enumeration constants, then TH does the case analysis on those constants and... |
| 2025-03-11 16:53:32 +0100 | CiaoSen | (~Jura@2a02:8071:64e1:7180::ac59) (Ping timeout: 268 seconds) |
| 2025-03-11 16:50:02 +0100 | <tomsmeding> | right, that's another one that does work |
| 2025-03-11 16:49:12 +0100 | <monochrom> | Currently there is just a very simple special case in use: for exam papers, use a TeX boolean flag and write like \ifsolution{ Answer: 42 }\else{ \vspace{2cm} }\fi |
| 2025-03-11 16:48:42 +0100 | <tomsmeding> | one such splitting approach I did once use is a toggle for switching between an anonymised (for submission to the conference) and a non-anonymised (for submission to arXiv) version of a LaTeX paper. The differences were small enough that that worked quite fine |
| 2025-03-11 16:47:09 +0100 | <tomsmeding> | it's likely to have more structure. |
| 2025-03-11 16:46:58 +0100 | <tomsmeding> | I'm going to make a stronger statement: if you're trying to automate such splitting for documents for human consumption, I'd rather read the original, pre-splitting |
| 2025-03-11 16:46:56 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 244 seconds) |
| 2025-03-11 16:45:16 +0100 | <tomsmeding> | multiple targets for computer consumption is something the field of CS has been working at solving for the past decades already, and we have various acceptable solutions :) |
| 2025-03-11 16:44:47 +0100 | <tomsmeding> | now, if at most one target is a document for human consumption, then it can work perfectly fine -- that's called literate programming |
| 2025-03-11 16:44:17 +0100 | <tomsmeding> | you'll always need bespoke formulations or connecting remarks/sentences, or layout fixes, etc. |
| 2025-03-11 16:43:49 +0100 | <tomsmeding> | honestly I expect that with this kind of stuff, where the end products are supposed to be documents for human consumption, you'll never be able to properly automate such splitting |
| 2025-03-11 16:43:22 +0100 | <monochrom> | \∩/ empirical data! |
| 2025-03-11 16:43:00 +0100 | <geekosaur> | I actually did my resume that way once since I was targeting multiple fields. It was an unmaintainable monster, and I ended up splitting it again |
| 2025-03-11 16:42:48 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-11 16:38:13 +0100 | <tomsmeding> | I'm afraid you'll have to work harder to get mad :) |
| 2025-03-11 16:37:59 +0100 | <tomsmeding> | indeed, the fact that you recognised that it _was_ a mad idea, proves that you aren't! |
| 2025-03-11 16:37:35 +0100 | <tomsmeding> | monochrom: having mad ideas occasionally does not mean one is mad |
| 2025-03-11 16:37:05 +0100 | <monochrom> | (Five minutes later, I recognized that obviously this would be a Frankenstein's monster on par with PL/I, UML, USB, ... so I didn't pursue further.) |
| 2025-03-11 16:37:05 +0100 | <monochrom> | To prove just how mad I am: Do you resent that for every research result, you have to write a tech report, and a conference paper, and a talk for that, and a journal paper, and a thesis? Well in the last days of my PhD, I had this mad idea: A markup language so you write the stuff just once in one file, the markup will tell the computer what to extract for the tech report, what to extract for the conference paper, what to extract for the talk... |
| 2025-03-11 16:34:27 +0100 | <tomsmeding> | and there is a `buildable: False` declaration you can put in a *.cabal file in case you have a configuration that you want to disallow |
| 2025-03-11 16:34:01 +0100 | <tomsmeding> | more generally, you can branch on the GHC version in a *.cabal file |
| 2025-03-11 16:33:46 +0100 | <tomsmeding> | euouae: at present, GHC is hard-bound to `base`, so version-bounding `base` also means version-bounding GHC |