Newest at the top
2025-02-13 02:41:37 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
2025-02-13 02:39:09 +0100 | tri | (~tri@ool-44c70bcb.dyn.optonline.net) (Ping timeout: 268 seconds) |
2025-02-13 02:36:41 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
2025-02-13 02:34:25 +0100 | tri | (~tri@ool-44c70bcb.dyn.optonline.net) |
2025-02-13 02:25:42 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
2025-02-13 02:25:37 +0100 | xff0x | (~xff0x@2405:6580:b080:900:eaaa:e5a8:7fd2:7c37) (Ping timeout: 248 seconds) |
2025-02-13 02:24:33 +0100 | user363627 | (~user@user/user363627) (Ping timeout: 248 seconds) |
2025-02-13 02:21:19 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
2025-02-13 02:21:04 +0100 | weary-traveler | (~user@user/user363627) user363627 |
2025-02-13 02:19:39 +0100 | <monochrom> | I use that too. |
2025-02-13 02:19:02 +0100 | <jackdk> | monochrom: `-fdefer-type-errors` is occasionally really useful as a "just let me play with the working bits in GHCi" hammer |
2025-02-13 02:14:26 +0100 | ryanbooker | (uid4340@id-4340.hampstead.irccloud.com) ryanbooker |
2025-02-13 02:13:26 +0100 | <monochrom> | Oh, maybe it means runtime type checks for scheme. |
2025-02-13 02:11:28 +0100 | sprotte24 | (~sprotte24@p200300d16f0a8e003d8337fe7ef7e64f.dip0.t-ipconnect.de) (Quit: Leaving) |
2025-02-13 02:10:34 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds) |
2025-02-13 02:06:41 +0100 | <monochrom> | err, turns off! |
2025-02-13 02:06:31 +0100 | <monochrom> | would be funny if GHC -Ooo turns on type checking. April 1st project! |
2025-02-13 02:05:57 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
2025-02-13 02:05:18 +0100 | <monochrom> | You can pretty much analogize ghc : O1 : O2 :: gcc : O2 : O3 |
2025-02-13 02:04:45 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 246 seconds) |
2025-02-13 02:00:32 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
2025-02-13 01:56:54 +0100 | <zwro> | great thanks |
2025-02-13 01:55:11 +0100 | <geekosaur> | otherwise no, just compilation speed (and performance of the resulting program, which can be pretty bad at -O0 especially if you were relying on fusion) |
2025-02-13 01:54:57 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
2025-02-13 01:54:23 +0100 | <geekosaur> | it will impact profiling unless you use a sufficiently recent ghc with -fprof-late |
2025-02-13 01:54:02 +0100 | <zwro> | i know i will still get typechecking in haskell :p |
2025-02-13 01:53:35 +0100 | <jackdk> | You'll still get typechecking but your compilation speed may be slower at higher optimisation levels |
2025-02-13 01:50:34 +0100 | Tuplanolla | (~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Quit: Leaving.) |
2025-02-13 01:50:33 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
2025-02-13 01:49:17 +0100 | <zwro> | if there was some reason i shouldn't have optimization turned on by default while developing |
2025-02-13 01:48:42 +0100 | califax_ | califax |
2025-02-13 01:48:28 +0100 | <zwro> | i just found out that in some scheme implementations, high optimization levels turn off type checking so i thought to ask here |
2025-02-13 01:48:12 +0100 | califax | (~califax@user/califx) (Ping timeout: 264 seconds) |
2025-02-13 01:47:44 +0100 | <zwro> | well i guess my question goes for any optimization level |
2025-02-13 01:47:31 +0100 | califax_ | (~califax@user/califx) califx |
2025-02-13 01:47:13 +0100 | <zwro> | i actually meant -O2 but this was funny |
2025-02-13 01:47:05 +0100 | euouae | (~euouae@user/euouae) () |
2025-02-13 01:43:23 +0100 | JuanDaugherty | ColinRobinson |
2025-02-13 01:40:13 +0100 | <c_wraith> | https://downloads.haskell.org/ghc/latest/docs/users_guide/ghc.html#optimization-levels I suppose it's technically documented... |
2025-02-13 01:39:49 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds) |
2025-02-13 01:39:44 +0100 | <geekosaur> | my conjecture is it helps for some corporate users |
2025-02-13 01:39:03 +0100 | <geekosaur> | it's documented, and the documentation more or less says what I just did |
2025-02-13 01:38:48 +0100 | <geekosaur> | yeh, my understanding is that it adds a lot to compile time but only produces speedups in some rare edge cases |
2025-02-13 01:38:47 +0100 | <c_wraith> | is it documented?\ |
2025-02-13 01:38:28 +0100 | <haskellbridge> | <sm> but it exists for _some_ reason... |
2025-02-13 01:38:05 +0100 | <haskellbridge> | <sm> people always say it does nothing... |
2025-02-13 01:37:29 +0100 | <zwro> | are there arguments against using -O3 in development besides longer compilation time? |
2025-02-13 01:34:00 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
2025-02-13 01:28:33 +0100 | ljdarj1 | ljdarj |
2025-02-13 01:28:33 +0100 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 248 seconds) |