Newest at the top
| 2024-05-06 15:27:44 +0200 | rosco | (rosco@gateway/vpn/airvpn/rosco) (Client Quit) |
| 2024-05-06 15:27:23 +0200 | rosco | (rosco@gateway/vpn/airvpn/rosco) |
| 2024-05-06 15:26:24 +0200 | tri | (~tri@ool-18bbef1a.static.optonline.net) (Ping timeout: 255 seconds) |
| 2024-05-06 15:25:31 +0200 | rosco | (~rosco@yp-146-6.tm.net.my) (Ping timeout: 255 seconds) |
| 2024-05-06 15:21:50 +0200 | tri | (~tri@ool-18bbef1a.static.optonline.net) |
| 2024-05-06 15:21:03 +0200 | ChaiTRex | (~ChaiTRex@user/chaitrex) (Quit: ChaiTRex) |
| 2024-05-06 15:15:18 +0200 | tzh | (~tzh@c-73-164-206-160.hsd1.or.comcast.net) |
| 2024-05-06 15:04:56 +0200 | [Leary] | (~Leary]@user/Leary/x-0910699) |
| 2024-05-06 15:04:41 +0200 | [Leary] | (~Leary]@user/Leary/x-0910699) (Remote host closed the connection) |
| 2024-05-06 15:02:58 +0200 | <yushyin> | so the warning is reasonable :-) |
| 2024-05-06 15:02:24 +0200 | rosco | (~rosco@yp-146-6.tm.net.my) |
| 2024-05-06 14:59:50 +0200 | <L29Ah> | yes, tab stops customization is incompatible with haskell |
| 2024-05-06 14:59:37 +0200 | <yushyin> | more reason not to use tabs i guess |
| 2024-05-06 14:57:54 +0200 | <opqdonut> | at which point, why bother? since the point of tabs (for some people) is to customize the tab stops |
| 2024-05-06 14:57:35 +0200 | <opqdonut> | L29Ah: right, yes, it's possible to get it to work, but it's not tabstop-independent |
| 2024-05-06 14:57:10 +0200 | <yushyin> | opqdonut: i see |
| 2024-05-06 14:56:46 +0200 | <L29Ah> | opqdonut: https://0x0.st/X8rC.txt |
| 2024-05-06 14:56:24 +0200 | <opqdonut> | or 1 column, I should say |
| 2024-05-06 14:56:18 +0200 | <opqdonut> | no he's right, it's only until the next tabstop, i.e. 1 space in that case |
| 2024-05-06 14:55:52 +0200 | <yushyin> | for the layout rule it's 8 'characters' or columns so to say |
| 2024-05-06 14:55:26 +0200 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Quit: = "") |
| 2024-05-06 14:54:39 +0200 | <L29Ah> | yushyin: \t in "foobarb\t" is one character wide |
| 2024-05-06 14:54:29 +0200 | <opqdonut> | you can circumvent this by splitting lines after "of", but that's not the common style |
| 2024-05-06 14:54:09 +0200 | <opqdonut> | you need spaces to line up things like: case myVeryLongIdentifierName of Just x -> e\n Nothing -> f |
| 2024-05-06 14:53:44 +0200 | <yushyin> | i didn't say spaces as in ' ' on purpose |
| 2024-05-06 14:53:15 +0200 | atwm | (~atwm@19-193-28-81.ftth.cust.kwaoo.net) |
| 2024-05-06 14:52:56 +0200 | <opqdonut> | yeah, you're right, the report specifies tabstops as 8 chars, not tab=8 spaces. |
| 2024-05-06 14:52:27 +0200 | <L29Ah> | "next tabstop" ≠ "n spaces" |
| 2024-05-06 14:51:50 +0200 | <L29Ah> | no |
| 2024-05-06 14:51:50 +0200 | <L29Ah> | 14:50:29]<yushyin> afaik, the haskell report defines a tab as whitespace with 8 characters in the layout rule |
| 2024-05-06 14:51:32 +0200 | <L29Ah> | no |
| 2024-05-06 14:51:32 +0200 | <L29Ah> | 14:48:41]<opqdonut> to get things to line up, you pretty much need to use spaces in addition to tabs |
| 2024-05-06 14:51:22 +0200 | <opqdonut> | see https://www.haskell.org/onlinereport/haskell2010/haskellch10.html#x17-17800010.3 |
| 2024-05-06 14:51:15 +0200 | <opqdonut> | yeah, I was just about to mention this as well |
| 2024-05-06 14:50:29 +0200 | <yushyin> | afaik, the haskell report defines a tab as whitespace with 8 characters in the layout rule |
| 2024-05-06 14:49:41 +0200 | <opqdonut> | it's probably possible to come up with a code style that uses only tabs, but it won't be idiomatic |
| 2024-05-06 14:49:15 +0200 | <opqdonut> | ... and mixing tabs and spaces is often confusing, especially if you have multiple people with different editor configs working on the codebase |
| 2024-05-06 14:48:41 +0200 | <opqdonut> | to get things to line up, you pretty much need to use spaces in addition to tabs |
| 2024-05-06 14:48:07 +0200 | <opqdonut> | haskell uses layout, which means that certain things must be in the same column (e.g. the | of guards) |
| 2024-05-06 14:43:49 +0200 | raehik | (~raehik@rdng-25-b2-v4wan-169990-cust1344.vm39.cable.virginm.net) |
| 2024-05-06 14:42:03 +0200 | <Slendi> | Thank you |
| 2024-05-06 14:40:03 +0200 | <Slendi> | Alright so it shouldnt be an issue if my codebase uses tabs or spaces to the language |
| 2024-05-06 14:39:31 +0200 | <Slendi> | yeah i did |
| 2024-05-06 14:39:07 +0200 | <Hecate> | you can disable it |
| 2024-05-06 14:39:04 +0200 | <Hecate> | yep, I believe the warning is to avoid accidental tabulations in a file where spaces are usually used |
| 2024-05-06 14:38:41 +0200 | <Hecate> | Tabs are a bonus for accessibility because people with impaired vision can set to be bigger |
| 2024-05-06 14:38:37 +0200 | <Slendi> | I am asking because I use tabs personally in all my code and when I compiled my code it gave me a warning and found that interesting |
| 2024-05-06 14:37:56 +0200 | <Hecate> | ah, this is a big debate |
| 2024-05-06 14:30:59 +0200 | <Slendi> | Hello, is there a reason why spaces are prefered for indentation rather than something like tabs? |
| 2024-05-06 14:30:28 +0200 | raehik | (~raehik@rdng-25-b2-v4wan-169990-cust1344.vm39.cable.virginm.net) (Ping timeout: 268 seconds) |