Newest at the top
| 2025-03-26 20:18:22 +0100 | <monochrom> | If you s/simple haskell/industrial haskell/ you begin to see why, for example, OverloadedStrings makes it into level 0. |
| 2025-03-26 20:17:57 +0100 | <EvanR> | and StrictData |
| 2025-03-26 20:17:24 +0100 | <EvanR> | OverlappingInstances is lumped into the same "don't use this" as DataKinds |
| 2025-03-26 20:17:10 +0100 | <geekosaur> | (except hierarchical modules and maybe FFI) |
| 2025-03-26 20:16:39 +0100 | <geekosaur> | -XHaskell98, no extensions 🙂 |
| 2025-03-26 20:15:58 +0100 | <EvanR> | RankNTypes? I mean yes, it's great. Is it simple haskell though? |
| 2025-03-26 20:15:49 +0100 | <haskellbridge> | <Morj> A weak version of antifeatures is warnings, like -Wincomplete-record-updates |
| 2025-03-26 20:15:31 +0100 | <EvanR> | OverloadedStrings is in level 0 "use at will never causes problems" category |
| 2025-03-26 20:15:09 +0100 | <geekosaur> | you can sort of do that with hlint btw |
| 2025-03-26 20:15:02 +0100 | <EvanR> | https://gist.github.com/mightybyte/6c469c125eb50e0c2ebf4ae26b5adfff |
| 2025-03-26 20:14:55 +0100 | <EvanR> | I found kind of a ridiculous list |
| 2025-03-26 20:14:51 +0100 | <monochrom> | It is still valuable to declare what you ignore, and the machine checks that you really haven't used that. |
| 2025-03-26 20:14:45 +0100 | <EvanR> | I scrolled down to see what to ignore |
| 2025-03-26 20:13:31 +0100 | euphores | (~SASL_euph@user/euphores) euphores |
| 2025-03-26 20:13:01 +0100 | <monochrom> | It states a vision that by now has long fizzled. |
| 2025-03-26 20:12:36 +0100 | <monochrom> | It doesn't really state which parts to ignore. |
| 2025-03-26 20:11:42 +0100 | <EvanR> | like simplehaskell.org |
| 2025-03-26 20:11:12 +0100 | <EvanR> | it would be simpler to just ignore parts of the language |
| 2025-03-26 20:11:04 +0100 | <monochrom> | I can. Half of the language is removed, and the remaining half is not even what I want. OK I'm just joking. >:) |
| 2025-03-26 20:10:27 +0100 | rvalue- | rvalue |
| 2025-03-26 20:08:49 +0100 | euphores | (~SASL_euph@user/euphores) (Quit: Leaving.) |
| 2025-03-26 20:08:07 +0100 | <yin> | the more i think of it the less i find arguments against it |
| 2025-03-26 20:04:41 +0100 | rvalue | (~rvalue@user/rvalue) (Ping timeout: 268 seconds) |
| 2025-03-26 20:04:22 +0100 | <yin> | we should have language contractions, where features could be optionally removed from the language, and then have the most popular retractions crystalize with new language versions |
| 2025-03-26 20:03:50 +0100 | rvalue- | (~rvalue@user/rvalue) rvalue |
| 2025-03-26 20:00:49 +0100 | caconym | (~caconym@user/caconym) caconym |
| 2025-03-26 20:00:12 +0100 | zungi | (~tory@user/andrewchawk) (Ping timeout: 264 seconds) |
| 2025-03-26 20:00:08 +0100 | caconym | (~caconym@user/caconym) (Quit: bye) |
| 2025-03-26 19:59:44 +0100 | jco | (~jco@78-70-217-44-no600.tbcn.telia.com) jco |
| 2025-03-26 19:58:15 +0100 | sarna | (~sarna@d192-22.icpnet.pl) () |
| 2025-03-26 19:53:29 +0100 | <monochrom> | Do people even first check whether their post is readable before sharing the link? I guess they don't care. |
| 2025-03-26 19:52:47 +0100 | <monochrom> | It's why whenever someone posts something on pastebin.com, I just click "raw" and be done with it. |
| 2025-03-26 19:52:25 +0100 | ash3en | (~Thunderbi@185.209.196.192) ash3en |
| 2025-03-26 19:51:24 +0100 | <geekosaur> | but IMO that's their fault, not that of string gaps |
| 2025-03-26 19:51:10 +0100 | <geekosaur> | well, part of it is many syntax color mechanisms fail badly with them |
| 2025-03-26 19:50:49 +0100 | weary-traveler | (~user@user/user363627) (Remote host closed the connection) |
| 2025-03-26 19:49:48 +0100 | <EvanR> | I can't stand a 1/2 pixel difference on my 3 subpixels |
| 2025-03-26 19:48:52 +0100 | <monochrom> | It is not a big deal to me, but I can see that a lot of other people can't stand it. (Hell, they can't even stand a half-pixel difference in 1pt fonts.) |
| 2025-03-26 19:47:34 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2025-03-26 19:46:58 +0100 | <monochrom> | OK the annoying part of string gaps that is relieved by MultilineStrings is that I have to manually enter \n for the former when I want it. |
| 2025-03-26 19:46:17 +0100 | <haskellbridge> | <Bowuigi> And if that's the case, arena allocators should be easy to automatically insert on linear languages. That could make Perceus fast or something |
| 2025-03-26 19:45:30 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 272 seconds) |
| 2025-03-26 19:45:28 +0100 | <haskellbridge> | <Bowuigi> Because the evidence translation technique from the Gaster & Jones paper on row types looks suspiciously similar to an arena/bump allocator |
| 2025-03-26 19:44:46 +0100 | <haskellbridge> | <Bowuigi> Small aside, do allocations in linear languages correspond to variable copying (+ an initial pool)? |
| 2025-03-26 19:41:01 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-26 19:39:18 +0100 | <monochrom> | Probably just because chronologically every extension must first prove itself to be compatible (or almost) with older extensions. |
| 2025-03-26 19:39:02 +0100 | <yin> | and how little syntactic minimalism is valued |
| 2025-03-26 19:38:10 +0100 | <yin> | i'm always amazed at how we the mountain of extensions keeps rising without much conflict |
| 2025-03-26 19:37:55 +0100 | <monochrom> | But here-doc syntax would be nicer. :) |
| 2025-03-26 19:37:05 +0100 | <monochrom> | I find string gaps usable. |