Newest at the top
2024-10-31 13:18:53 +0100 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en) |
2024-10-31 13:13:33 +0100 | lortabac | (~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) lortabac |
2024-10-31 13:04:24 +0100 | <Leonard26> | Ok, I'll try that, thank you :] |
2024-10-31 13:03:33 +0100 | <kaol> | Use it with forkIO. |
2024-10-31 13:03:12 +0100 | <Leonard26> | I actually tried threadDelay but it stops my application from running. I need the application to be running '=D |
2024-10-31 13:02:35 +0100 | <kaol> | My recommendation is to start with Control.Concurrent and if it start to feel too restraining, have a look at Control.Concurrent.Async next. |
2024-10-31 13:02:01 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 244 seconds) |
2024-10-31 13:01:44 +0100 | <kaol> | With Control.Concurrent, it's like forkIO (threadDelay 123456 >> doStuff). If you want to cancel it, use the thread id to killThread it. |
2024-10-31 13:00:10 +0100 | <Leonard26> | Thank you for your answer. I'm still a begginer programmer, I just need to be able to call a function after x seconds have passed. Can I still do it without this package then? |
2024-10-31 12:59:06 +0100 | comerijn | (~merijn@77.242.116.146) merijn |
2024-10-31 12:58:16 +0100 | weary-traveler | (~user@user/user363627) user363627 |
2024-10-31 12:58:00 +0100 | img | (~img@user/img) img |
2024-10-31 12:57:54 +0100 | <kaol> | Leonard26: I've no personal experience with these modules but looks like it's indeed not available on Windows. It uses some OS specific C calls. I looked at delay too and I'm thinking that you could very likely do everything it offers with async library and Control.Concurrent from base, too. Do you have some other reason for going with delay? |
2024-10-31 12:56:36 +0100 | img | (~img@user/img) (Quit: ZNC 1.8.2 - https://znc.in) |
2024-10-31 12:55:18 +0100 | euleritian | (~euleritia@dynamic-176-007-007-025.176.7.pool.telefonica.de) (Ping timeout: 252 seconds) |
2024-10-31 12:49:24 +0100 | CiaoSen | (~Jura@2a05:5800:484:d00:ca4b:d6ff:fec1:99da) CiaoSen |
2024-10-31 12:44:07 +0100 | euleritian | (~euleritia@dynamic-176-007-007-025.176.7.pool.telefonica.de) |
2024-10-31 12:43:49 +0100 | euleritian | (~euleritia@dynamic-176-007-007-025.176.7.pool.telefonica.de) (Ping timeout: 252 seconds) |
2024-10-31 12:43:39 +0100 | <Leonard26> | This is the GHC.Event module |
2024-10-31 12:43:38 +0100 | <Leonard26> | https://www.stackage.org/haddock/lts-22.39/base-4.18.2.1/GHC-Event.html |
2024-10-31 12:41:25 +0100 | <Leonard26> | This is his comment |
2024-10-31 12:41:24 +0100 | <Leonard26> | CommentedJan 7, 2014 at 12:29 |
2024-10-31 12:41:24 +0100 | <Leonard26> | mhwombat |
2024-10-31 12:41:23 +0100 | <Leonard26> | In searching for info, I stumbled upon some info that deepens my suspicion that GHC.Event is not available on Windows, at least not on the 32-bit OS: In the source code for GHC.Conc.IO, all of the imports of GHC.Event are surrounded by #ifdef mingw32_HOST_OS ... else .. endif blocks. – |
2024-10-31 12:39:59 +0100 | <Leonard26> | https://stackoverflow.com/questions/20969432/how-to-import-ghc-event |
2024-10-31 12:39:59 +0100 | <Leonard26> | https://www.stackage.org/lts-22.20 |
2024-10-31 12:39:58 +0100 | <Leonard26> | https://hackage.haskell.org/package/delay-0 |
2024-10-31 12:39:58 +0100 | <Leonard26> | upon installation and running *stack build* again the same error occured again. Looking around I found an article on stackoverflow where the user who made the question was beginning to think that the module wasn't available for windows at all. Do you know anything about this? Is there a workaround for it? |
2024-10-31 12:39:57 +0100 | <Leonard26> | Hello! I am trying to build a package named *delay* but I am having some trouble. I am working on Windows. *stack build* command throw an error saying Could not find module 'GHC.Event'. I have checked in my ghc directory and couldn't find it so I tried installing another version from stackage, lts-22.20 for ghc 9.6.4, that appearently had it but |
2024-10-31 12:37:11 +0100 | morb | (~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 255 seconds) |
2024-10-31 12:35:21 +0100 | euleritian | (~euleritia@dynamic-176-007-007-025.176.7.pool.telefonica.de) |
2024-10-31 12:32:46 +0100 | morb | (~morb@pool-108-41-100-120.nycmny.fios.verizon.net) |
2024-10-31 12:31:41 +0100 | Leonard26 | (~Leonard26@49.236.10.26) |
2024-10-31 12:25:43 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) ChaiTRex |
2024-10-31 12:25:09 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) (Remote host closed the connection) |
2024-10-31 12:25:03 +0100 | szkl | (uid110435@id-110435.uxbridge.irccloud.com) szkl |
2024-10-31 12:23:15 +0100 | jespada | (~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net) jespada |
2024-10-31 12:20:49 +0100 | euleritian | (~euleritia@dynamic-176-007-016-079.176.7.pool.telefonica.de) (Ping timeout: 248 seconds) |
2024-10-31 12:14:22 +0100 | jespada | (~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net) (Quit: Textual IRC Client: www.textualapp.com) |
2024-10-31 12:12:58 +0100 | rvalue | (~rvalue@user/rvalue) rvalue |
2024-10-31 12:12:39 +0100 | rvalue | (~rvalue@user/rvalue) (Ping timeout: 276 seconds) |
2024-10-31 12:08:50 +0100 | euleritian | (~euleritia@dynamic-176-007-016-079.176.7.pool.telefonica.de) |
2024-10-31 12:07:13 +0100 | <kuribas> | And ghc is quite capable. |
2024-10-31 12:06:44 +0100 | <kuribas> | Which is not surprising. Just using C++ doesn't garantee automatically being fast. |
2024-10-31 12:04:12 +0100 | euleritian | (~euleritia@dynamic-176-007-016-079.176.7.pool.telefonica.de) (Ping timeout: 276 seconds) |
2024-10-31 12:03:59 +0100 | <Inst> | tomsmeding: apparently some C++-er learned Haskell, and found that their Haskell code was performing 80% as well as their C++ code. |
2024-10-31 12:02:04 +0100 | caconym | (~caconym@user/caconym) caconym |
2024-10-31 12:01:46 +0100 | kenran | (~user@user/kenran) (Remote host closed the connection) |
2024-10-31 12:00:04 +0100 | caconym | (~caconym@user/caconym) (Quit: bye) |
2024-10-31 11:56:24 +0100 | CiaoSen | (~Jura@2a05:5800:484:d00:ca4b:d6ff:fec1:99da) (Ping timeout: 260 seconds) |