2025/03/01

Newest at the top

2025-03-01 12:28:02 +0100 <tomsmeding> (I have that set, as well as haskell.plugin.stan.globalOn = false)
2025-03-01 12:27:38 +0100tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Quit: zzz)
2025-03-01 12:27:37 +0100 <euouae> thank you!!
2025-03-01 12:24:45 +0100 <tomsmeding> Leary: I've actually seen that before, it's genius
2025-03-01 12:23:05 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 265 seconds)
2025-03-01 12:18:32 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-03-01 12:17:56 +0100 <tomsmeding> the setting you need to set is haskell.plugin.hlint.globalOn = false
2025-03-01 12:17:37 +0100 <tomsmeding> euouae: figure out where you put language server configuration in your emacs LSP client
2025-03-01 12:14:33 +0100talismanick(~user@2601:644:937c:ed10::ae5) (Ping timeout: 245 seconds)
2025-03-01 12:14:21 +0100 <euouae> I've tried to turn them off selectively I'm thinking that I just don't want them at all
2025-03-01 12:13:56 +0100 <euouae> You're moving the cursor point on a symbol to see its type and boom Clippy pops up "It looks like you're not optimizing your endofunctors here"
2025-03-01 12:13:08 +0100 <euouae> holy cow they're annoying on emacs
2025-03-01 12:13:03 +0100 <euouae> Does anyone know how I can turn off all the hlint recommendations
2025-03-01 12:12:22 +0100talisman`(~user@2601:644:937c:ed10::ae5)
2025-03-01 12:06:26 +0100lxsameer(~lxsameer@Serene/lxsameer) (Ping timeout: 252 seconds)
2025-03-01 11:59:29 +0100killy(~killy@terminal-3-187.retsat1.com.pl) (Ping timeout: 248 seconds)
2025-03-01 11:54:14 +0100 <Leary> tomsmeding: https://hackage.haskell.org/package/BASIC-0.1.5.0/docs/Language-BASIC.html
2025-03-01 11:52:26 +0100 <euouae> nice, thakn you
2025-03-01 11:51:55 +0100 <tomsmeding> you always need to list all modules that you're defining in the cabal file, either in other-modules or in exposed-modules (the latter relevant only for libraries)
2025-03-01 11:51:55 +0100__monty__(~toonn@user/toonn) toonn
2025-03-01 11:51:27 +0100 <tomsmeding> right, you need `other-modules: Tests` in the test-suite block in your cabal file
2025-03-01 11:51:27 +0100 <euouae> It's a warning-Wmissing-home-modules
2025-03-01 11:51:17 +0100 <euouae> naming Tests as the module
2025-03-01 11:51:10 +0100 <euouae> I get `These modules are needed for compilation but not listed in your .cabal file's other-modules for ‘leetcode-0.1.0.0-inplace-leetcode-test’ :`
2025-03-01 11:51:05 +0100 <tomsmeding> `import Tests`?
2025-03-01 11:50:55 +0100 <euouae> Tests.hs has the hedgehog generated/discovered tests, how can I import that in Main.hs?
2025-03-01 11:50:40 +0100 <euouae> Another stupid question, in my test/ I have Main.hs and Tests.hs
2025-03-01 11:50:28 +0100 <euouae> I get ti
2025-03-01 11:49:37 +0100 <tomsmeding> would that be `Exercises.12 input`? how would the parser even know what you mean tthere
2025-03-01 11:49:22 +0100 <lambdabot> True
2025-03-01 11:49:20 +0100 <tomsmeding> > Data.Maybe.isJust (Just 42)
2025-03-01 11:49:14 +0100 <tomsmeding> euouae: imagine what would happen if you would try to use such a module qualified
2025-03-01 11:48:35 +0100 <euouae> Okay, thank you. I'm actually thinking I'll just keep it all in one flat file
2025-03-01 11:48:22 +0100 <tomsmeding> yes
2025-03-01 11:48:19 +0100 <euouae> Perhaps I can do something like E123.hs for exercise 123?
2025-03-01 11:47:58 +0100 <tomsmeding> and module names must start with a capital letter
2025-03-01 11:47:53 +0100 <tomsmeding> in a cabal project, a module file must always have the module name as its file name
2025-03-01 11:47:39 +0100 <tomsmeding> but as a single file, HLS is okay with it for me
2025-03-01 11:47:36 +0100 <euouae> oh yeah, I use cabal
2025-03-01 11:47:27 +0100 <tomsmeding> it's not a valid file name in a cabal project
2025-03-01 11:47:26 +0100 <euouae> anyway right now I just have all the solutions in one file separated by -- *
2025-03-01 11:47:21 +0100 <tomsmeding> works perfectly fine for me
2025-03-01 11:47:03 +0100 <euouae> I'm doing some leetcode challenges but 123.hs is bad I think
2025-03-01 11:46:57 +0100 <tomsmeding> we were getting so close!
2025-03-01 11:46:37 +0100 <euouae> tomsmeding: oh sorry, I mean file *names*
2025-03-01 11:43:42 +0100 <tomsmeding> it's as close as you're going to get to "including" a "number", really
2025-03-01 11:43:22 +0100 <tomsmeding> mauke: on second thoughts I'm starting to like your last suggestion
2025-03-01 11:41:23 +0100 <tomsmeding> that's about as reasonable an interpretation as claiming that they're used to macOS and actually meant a spreadsheet
2025-03-01 11:40:37 +0100 <mauke> #include "/dev/fd/0"
2025-03-01 11:40:31 +0100 <mauke> oh, I just thought of another way to "include numbers in my source files"