Home freenode/#haskell: Logs Calendar

Logs: freenode/#haskell

←Prev  Next→
Page 1 .. 207 208 209 210 211 212 213 214 215 216 217 .. 5022
— 502,152 events total
2020-09-25 19:07:55 → mu__ joins (~mu@unaffiliated/mu)
2020-09-25 19:09:04 → kenran joins (~maier@mue-88-130-62-135.dsl.tropolys.de)
2020-09-25 19:09:56 × frdg quits (47b88ff9@pool-71-184-143-249.bstnma.fios.verizon.net) (Remote host closed the connection)
2020-09-25 19:12:45 → merijn joins (~merijn@83-160-49-249.ip.xs4all.nl)
2020-09-25 19:13:38 <pie_> the problem i run into a lot is i dont know which piece of code is causing the error
2020-09-25 19:13:41 × jedws quits (~jedws@2001:8003:337f:1b00:edc3:4bd4:30b0:401b) (Quit: My MacBook has gone to sleep. ZZZzzz…)
2020-09-25 19:13:45 <pie_> i also have no idea when backtracking triggers :P
2020-09-25 19:14:02 × cole-h quits (~cole-h@c-73-48-197-220.hsd1.ca.comcast.net) (Quit: Goodbye)
2020-09-25 19:14:21 <pie_> though my code so far afaik doesnt have any deliberate backtracking, so if backtracking happens its probably by mistake
2020-09-25 19:15:47 → cr3 joins (~cr3@192-222-143-195.qc.cable.ebox.net)
2020-09-25 19:16:18 × fluturel quits (~fluturel@82.137.14.51) (Quit: leaving)
2020-09-25 19:16:44 Lycurgus had to look at the log, backtracking in hs sounded funny
2020-09-25 19:16:57 <hyperisco> combinators are supposed to be syntactically relatable to grammar notation like BNF
2020-09-25 19:17:10 <hyperisco> so you are supposed to be able to understand the grammar that way
2020-09-25 19:17:26 × mu__ quits (~mu@unaffiliated/mu) (Read error: Connection reset by peer)
2020-09-25 19:17:35 <ski> (some familiarity with Prolog, and perhaps in particular DCG, might help)
2020-09-25 19:17:54 → mu joins (~mu@unaffiliated/mu)
2020-09-25 19:18:04 <hyperisco> the complication is to watch out for restricted grammar classes (most combinators do not support all CFG)
2020-09-25 19:18:13 × merijn quits (~merijn@83-160-49-249.ip.xs4all.nl) (Ping timeout: 264 seconds)
2020-09-25 19:18:59 <hyperisco> I'd just use combinators that do support all CFG if confusion is the main problem
2020-09-25 19:20:45 × Mcdukc quits (~oleg@90.255.27.8) (Read error: Connection reset by peer)
2020-09-25 19:21:36 → v_m_v joins (~vm_v@2a02:aa12:3200:6480:f507:71a:9334:3099)
2020-09-25 19:22:32 → takuan joins (~takuan@178-116-218-225.access.telenet.be)
2020-09-25 19:22:48 <pie_> im parsing some text file generated by some government land office program
2020-09-25 19:22:57 → wroathe joins (~wroathe@c-68-54-25-135.hsd1.mn.comcast.net)
2020-09-25 19:22:58 <pie_> its not exactly parsing friendly but i havent seen any specs either so
2020-09-25 19:23:34 Lycurgus guesses that most hs parser things are ll or lr without backtracking
2020-09-25 19:23:34 <pie_> but yeah its not like i have some grammar to code against
2020-09-25 19:27:06 → crobbins joins (~crobbins@2600:1700:48eb:8490:4a3:9554:f20a:562c)
2020-09-25 19:27:28 × wroathe quits (~wroathe@c-68-54-25-135.hsd1.mn.comcast.net) (Ping timeout: 246 seconds)
2020-09-25 19:27:28 × mu quits (~mu@unaffiliated/mu) (Read error: Connection reset by peer)
2020-09-25 19:27:54 → mu joins (~mu@unaffiliated/mu)
2020-09-25 19:29:34 × bloodstalker quits (~bloodstal@46.166.187.178) (Ping timeout: 272 seconds)
2020-09-25 19:30:48 → nyd joins (~nyd@unaffiliated/elysian)
2020-09-25 19:34:56 <sm[m]> pie_: you need one of those debug functions I mentioned
2020-09-25 19:35:18 <sm[m]> glguy that's an interesting observation
2020-09-25 19:35:27 <hyperisco> pie_, if you suspect it is realisable as a CFG then I
2020-09-25 19:35:32 <hyperisco> 'd start there on paper
2020-09-25 19:35:44 <hyperisco> and only after succeeding with that worry about the program
2020-09-25 19:36:34 × v_m_v quits (~vm_v@2a02:aa12:3200:6480:f507:71a:9334:3099) (Remote host closed the connection)
2020-09-25 19:36:52 <hyperisco> some combinators instance Monad and can parse some grammars outside CFG
2020-09-25 19:37:16 <hyperisco> I think best to know the nature of what you're dealing with first
2020-09-25 19:37:28 × jneira quits (501e65ce@gateway/web/cgi-irc/kiwiirc.com/ip.80.30.101.206) (Ping timeout: 260 seconds)
2020-09-25 19:37:29 × mu quits (~mu@unaffiliated/mu) (Read error: Connection reset by peer)
2020-09-25 19:37:54 → mu joins (~mu@unaffiliated/mu)
2020-09-25 19:38:29 → coot joins (~coot@37.30.52.6.nat.umts.dynamic.t-mobile.pl)
2020-09-25 19:39:11 <sm[m]> pie_: maybe those functions won't work for you but it's worth building one, along the lines of https://hackage.haskell.org/package/hledger-lib-1.19.1/docs/Hledger-Utils-Debug.html#v:traceParse
2020-09-25 19:39:47 × sooch quits (~sooch@209.6.196.179) (Quit: leaving)
2020-09-25 19:39:56 <sm[m]> hyperisco: very true
2020-09-25 19:40:08 → frdg joins (47b88ff9@pool-71-184-143-249.bstnma.fios.verizon.net)
2020-09-25 19:40:48 <frdg> how does stack decide which version of ghc to use? I use ghcup. I would like the default ghc to be 8.8.3.
2020-09-25 19:41:07 <frdg> ghc --version returns a different ghc than 8.8.3
2020-09-25 19:41:17 <glguy> stack and ghcup are different things
2020-09-25 19:42:09 <frdg> so different stack versions use different ghc's ?
2020-09-25 19:42:10 → acidjnk_new joins (~acidjnk@p200300d0c7237802f9328c36b4a510ff.dip0.t-ipconnect.de)
2020-09-25 19:42:12 <geekosaur> stack installs its own ghc based on the selected/current resolver, and by default ignores any ghc from a different source
2020-09-25 19:42:23 <sm[m]> By the resolver in the nearest stack.yaml
2020-09-25 19:42:57 hackage bugsnag-hs 0.2.0.0 - A Bugsnag client for Haskell. https://hackage.haskell.org/package/bugsnag-hs-0.2.0.0 (JasperWoudenberg)
2020-09-25 19:43:11 <geekosaur> a differet stack release will probably default to a different resolver, but this can be configured by editing a stack.yaml somewhere (either in the current project, or a global default one)
2020-09-25 19:43:29 → isovector1 joins (~isovector@172.103.216.166)
2020-09-25 19:43:43 <frdg> oh ok. Now to my next question. How can I change my stack version from 2.3.3 to 2.4?
2020-09-25 19:44:26 <sm[m]> after that is released, stack upgrade (is one way)
2020-09-25 19:45:00 × geekosaur quits (42d52102@66.213.33.2) (Remote host closed the connection)
2020-09-25 19:45:23 × Lycurgus quits (~niemand@98.4.96.130) (Quit: Exeunt)
2020-09-25 19:45:34 <phadej> weird, I just noticed that stack-2.5 prerelease was tagged
2020-09-25 19:45:39 → johtso joins (uid563@gateway/web/irccloud.com/x-dfhkalrthzrhztaj)
2020-09-25 19:45:41 <phadej> I wonder what happened to 2.4 (well, not really)
2020-09-25 19:45:50 <phadej> https://github.com/commercialhaskell/stack/releases/tag/v2.5.0.1
2020-09-25 19:45:51 → v_m_v joins (~vm_v@2a02:aa12:3200:6480:f507:71a:9334:3099)
2020-09-25 19:46:02 <frdg> really? I have two machines. On one machine stack --version returns 2.4? When I run stack upgrade both machines say it is the most recent version.
2020-09-25 19:46:59 <phadej> or hmm. does stack use odd-even numbering (and oddly, with even numbers being development ones)
2020-09-25 19:47:16 <phadej> i.e. stack-2.4 is some development version?
2020-09-25 19:47:30 × mu quits (~mu@unaffiliated/mu) (Read error: Connection reset by peer)
2020-09-25 19:47:41 × johtso quits (uid563@gateway/web/irccloud.com/x-dfhkalrthzrhztaj) (Disconnected by services)
2020-09-25 19:47:54 → mu joins (~mu@unaffiliated/mu)
2020-09-25 19:48:13 × v_m_v quits (~vm_v@2a02:aa12:3200:6480:f507:71a:9334:3099) (Remote host closed the connection)
2020-09-25 19:48:24 → ubert joins (~Thunderbi@91.141.0.190.wireless.dyn.drei.com)
2020-09-25 19:49:18 → wroathe joins (~wroathe@c-68-54-25-135.hsd1.mn.comcast.net)
2020-09-25 19:49:35 <sm[m]> phadej: strange.. they haven't used that numbering
2020-09-25 19:50:24 <sm[m]> but I'm glad of the 5125 fix, that will speed up CI builds
2020-09-25 19:50:33 → Dablyon joins (~godel@173.171.157.121)
2020-09-25 19:50:45 <sm[m]> frdg: stranger still
2020-09-25 19:50:59 × kenran quits (~maier@mue-88-130-62-135.dsl.tropolys.de) (Ping timeout: 240 seconds)
2020-09-25 19:51:02 <phadej> sm[m]: there weren't 2.2 either
2020-09-25 19:51:08 → merijn joins (~merijn@83-160-49-249.ip.xs4all.nl)
2020-09-25 19:51:51 <sm[m]> they only release unstable versions ? :)
2020-09-25 19:52:15 × mirrorbird quits (~psutcliff@2a00:801:44a:a00b:20c3:c64:eb15:73a2) (Ping timeout: 272 seconds)
2020-09-25 19:52:19 <frdg> `Version 2.4.0, Git revision 1b1bed5b84b3aed76cf27b02cadd46d09efc611f PRE-RELEASE x86_64 hpack-0.33.0` It does say pre-release I guess?
2020-09-25 19:52:44 <frdg> everything is working regardless though so I am pretty happy.
2020-09-25 19:53:10 <sm[m]> ah, well that makes more sense. They must have changed their mind
2020-09-25 19:53:40 <sm[m]> or it's a dev version numbering scheme like phade said
2020-09-25 19:53:51 × heatsink quits (~heatsink@107-136-5-69.lightspeed.sntcca.sbcglobal.net) (Remote host closed the connection)
2020-09-25 19:54:10 × ggole quits (~ggole@2001:8003:8119:7200:4cc1:e316:a6d6:5aec) (Quit: Leaving)
2020-09-25 19:54:19 <sm[m]> a wrong one
2020-09-25 19:55:18 <sm[m]> though .0 releases are usually unstable so I suppose it's fair..
2020-09-25 19:55:32 × Dablyon quits (~godel@173.171.157.121) (Ping timeout: 272 seconds)
2020-09-25 19:56:14 <int-e> If 2.0 is a stable release then what version number do you use for the development release leadung up to it? I've seen things like 1.99 and it's ugly.
2020-09-25 19:56:47 <sm[m]> Ha that's my scheme. It's find it ok
2020-09-25 19:56:52 → heatsink joins (~heatsink@107-136-5-69.lightspeed.sntcca.sbcglobal.net)
2020-09-25 19:56:53 <sm[m]> I find it
←Prev  Next→
Page 1 .. 207 208 209 210 211 212 213 214 215 216 217 .. 5022

All times are in UTC.