00:08:18 | * | io2 quit (Quit: ...take irc away, what are you? genius, billionaire, playboy, philanthropist) |
00:08:23 | * | saml_ joined #nimrod |
00:08:48 | * | io2 joined #nimrod |
00:13:22 | bogen | https://gist.github.com/anonymous/6c39fbc6569ac47b94c2 |
00:13:58 | * | io2 quit (Quit: ...take irc away, what are you? genius, billionaire, playboy, philanthropist) |
00:21:15 | bogen | I got parseutils working in a compileTime proc, just not in that snippet |
00:24:57 | Araq | yeah |
00:25:02 | Araq | looks easy to fix though |
00:25:30 | Araq | I'm looking at it right now |
00:31:24 | fowl | does anybody have a recent windows build they can upload |
00:31:47 | Araq | fowl: nimbuild has packages |
00:31:57 | Araq | bogen: are you on the bigbreak branch? |
00:35:29 | fowl | grr 'Error: unhandled exception: The system cannot find the file specified. [EOS]' it could say what file was |
00:40:07 | * | Jesin quit (Quit: Leaving) |
00:45:01 | bogen | Araq: I don't think so. Let me check. |
00:45:42 | bogen | $ git branch --> * devel |
00:46:34 | NimBot | Araq/Nimrod bigbreak 31db3ae Araq [+0 ±1 -0]: minor bugfix for void .compileTime procs |
00:46:34 | NimBot | Araq/Nimrod bigbreak 8925d0e Araq [+0 ±4 -0]: minor improvement for nim pretty |
00:46:51 | Araq | bogen: well I fixed it on bigbreak |
00:47:07 | Araq | "minor bugfix for void .compileTime procs" |
00:47:15 | bogen | Araq: ok, thanks, I'll take a look |
00:47:20 | Araq | it's easy to merge it into devel |
00:47:28 | Araq | but I need to sleep now, good night |
00:47:44 | bogen | g'nite |
00:57:24 | * | Jesin joined #nimrod |
01:01:42 | * | renesac joined #nimrod |
02:31:17 | * | saml_ quit (Quit: Leaving) |
02:46:12 | * | q66 quit (Quit: Leaving) |
03:08:14 | * | EXetoC quit (Quit: WeeChat 1.0) |
03:37:30 | * | ARCADIVS joined #nimrod |
04:42:04 | * | bjz_ quit (Read error: Connection reset by peer) |
04:42:18 | * | bjz joined #nimrod |
05:05:59 | * | fowl quit (Ping timeout: 255 seconds) |
05:54:45 | * | renesac quit (Ping timeout: 240 seconds) |
06:13:52 | * | Varriount-Mobile joined #nimrod |
06:45:33 | * | BlaXpirit joined #nimrod |
07:32:21 | * | io2 joined #nimrod |
07:32:49 | * | io2 quit (Client Quit) |
08:18:24 | * | mal`` joined #nimrod |
09:13:02 | dom96 | good morning |
09:24:45 | Araq | hi dom96 |
09:25:10 | dom96 | hey sup? |
09:36:03 | Araq | fixing tests |
09:36:54 | Araq | and I'm reading about the "working branching model" |
09:37:07 | dom96 | filwit didn't show up :( |
09:37:21 | Araq | so that bugfixes are easier to push to devel/master |
09:51:15 | Araq | well I have the hope filwit is secretly working on all the promised stuff |
09:51:25 | Araq | and will show up tonight with breaking news |
09:51:40 | dom96 | yes |
09:51:47 | * | BlaXpirit quit (Quit: Quit Konversation) |
09:53:26 | * | BlaXpirit joined #nimrod |
10:21:05 | * | Matthias247 joined #nimrod |
10:23:22 | * | Varriount-Mobile quit (Ping timeout: 240 seconds) |
10:23:44 | * | Varriount-Mobile joined #nimrod |
10:25:00 | Araq | yay so tsets2 fails and I don't know since when |
10:25:18 | Araq | that's a horrible regression |
10:26:08 | Araq | and btw I hate this sets.isValid bullshit |
10:28:53 | dom96 | what does that do? |
10:32:24 | * | io2 joined #nimrod |
10:36:45 | Araq | some bullshit 'nil' checking for the poor people who cannot remember whether they properly initialized things |
10:38:53 | NimBot | Araq/Nimrod bigbreak 8aca51a Araq [+0 ±1 -0]: nim pretty: default is now to overwrite files |
10:38:53 | NimBot | Araq/Nimrod bigbreak 2d1b9d1 Araq [+0 ±3 -0]: ENDB compiles again |
10:38:53 | NimBot | Araq/Nimrod bigbreak dd830d2 Araq [+0 ±1 -0]: added ENDB warning |
10:38:53 | NimBot | Araq/Nimrod bigbreak ae548a6 Araq [+0 ±8 -0]: made some tests green |
10:38:53 | NimBot | 1 more commits. |
10:39:02 | Araq | bbl |
10:41:37 | * | Varriount-Mobile quit (Read error: Connection reset by peer) |
10:43:15 | * | EXetoC joined #nimrod |
11:08:19 | * | q66 joined #nimrod |
11:39:32 | * | io2 quit (Quit: ...take irc away, what are you? genius, billionaire, playboy, philanthropist) |
11:42:39 | * | io2 joined #nimrod |
11:55:04 | NimBot | Araq/Nimrod bigbreak eac71d3 Dominik Picheta [+0 ±1 -0]: s/storeFile/store/ |
11:55:04 | NimBot | Araq/Nimrod bigbreak d26d42b Dominik Picheta [+0 ±2 -0]: Case sensitivity fixes for httpclient and sockets module. |
11:55:04 | NimBot | Araq/Nimrod bigbreak bb1e87c Dominik Picheta [+0 ±5 -0]: Async SSL support. |
11:56:17 | * | Trustable joined #nimrod |
12:34:32 | * | ARCADIVS quit (Quit: WeeChat 0.4.3) |
12:37:14 | dom96 | Araq: Did you make all exceptions ref? |
12:37:32 | Araq | dom96: no, that would break too much code |
12:37:46 | Araq | or rather: pretty cannot handle that |
12:38:10 | dom96 | But it would allow raise Exception(msg: "foobar") :( |
12:42:24 | Araq | how did threads.nim ever compile? o.O |
12:42:32 | Araq | it's all wrong lol |
12:50:36 | * | exe joined #nimrod |
12:51:06 | * | [CBR]Unspoken joined #nimrod |
12:53:52 | * | darkf quit (Quit: Leaving) |
12:57:03 | * | EXetoC quit (*.net *.split) |
12:57:05 | * | [CBR]Unspoken1 quit (*.net *.split) |
13:08:36 | NimBot | Araq/Nimrod bigbreak 25e0c26 Dominik Picheta [+0 ±1 -0]: Added async implementation for smtp module. |
13:10:30 | * | zahary joined #nimrod |
13:10:57 | * | zahary1 quit (Read error: Connection reset by peer) |
13:16:06 | NimBot | Araq/Nimrod bigbreak 3ba34f1 Araq [+0 ±7 -0]: prettified re.nim; make some tests green |
13:16:06 | NimBot | Araq/Nimrod bigbreak 30823c1 Araq [+0 ±44 -0]: make tests green |
13:16:06 | NimBot | Araq/Nimrod bigbreak de29ce8 Araq [+0 ±7 -0]: Merge branch 'bigbreak' of https://github.com/Araq/Nimrod into bigbreak |
13:26:18 | NimBot | Araq/Nimrod bigbreak 93eb9c4 Araq [+0 ±4 -0]: more stdlib modules work |
13:28:22 | Araq | see you later |
13:54:51 | * | kunev joined #nimrod |
14:18:24 | * | demilichsd joined #nimrod |
14:18:47 | demilichsd | hey |
14:19:08 | demilichsd | just how feasible is using Nimrod for lower level systems programming, using the POSIX API wrapper and all that? |
14:19:12 | * | noam__ is now known as noam |
14:19:15 | demilichsd | I'm talking stuff like bootscript mechanisms |
14:20:11 | demilichsd | If it's suitable, then I really could consider spending more time with it and potentially getting away from the mundanities of C |
14:25:54 | dom96 | hi demilichsd |
14:26:04 | dom96 | I think it's very feasible. |
14:26:44 | dom96 | However I don't know much about how bootscript mechanisms are created. |
14:27:25 | dom96 | Most of posix is wrapped in lib/posix/posix.nim |
14:29:27 | demilichsd | Yes, as I saw. |
14:30:26 | * | Jehan_ joined #nimrod |
14:30:37 | * | exe is now known as EXetoC |
14:31:59 | EXetoC | dom96: raise (ref Exception)(msg: "foobar")? :p |
14:32:03 | EXetoC | or whatever the syntax was |
14:32:36 | dom96 | EXetoC: I'd rather just use newException in that case. |
14:37:44 | EXetoC | raiseException |
14:38:00 | EXetoC | though I often have a module-specific 'fail' proc |
14:40:21 | Jehan_ | I'm not a huge fan of having a hierarchy of exception types. |
14:41:11 | Jehan_ | This is, as far as I've been able to determine, a C++ invention that was implemented because it looked nice on paper, but without any practical experience what it would mean for software engineering practice. |
14:42:28 | dom96 | Jehan_: Do you have any examples of cases where it's a bad thing? |
14:42:29 | EXetoC | you don't think it's important to be able to catch specific types? |
14:42:50 | Jehan_ | EXetoC: I think that's part of what's fundamentally broken about it. |
14:42:50 | EXetoC | you want at least the base class I assume |
14:43:43 | EXetoC | ok.. |
14:43:44 | Jehan_ | If you have an exception handler that can make such fine-grained determination and assess appropriate error handling for each, then you probably don't need exceptions in the first place. |
14:43:54 | Jehan_ | You're then using them as non-local gotos. |
14:44:07 | Jehan_ | With difficult to validate semantics. |
14:45:12 | OrionPK | dom96 waitfor works well! |
14:45:13 | OrionPK | thanks :) |
14:46:03 | dom96 | OrionPK: yay, that's good to hear. |
14:47:00 | Araq | Jehan_: I used to agree with you, but nowadays I think it has some value |
14:47:26 | Jehan_ | There are really only two important classes of exceptions: (1) Something unforeseen happened that I couldn't programmatically avoid and which would result in undefined behavior if I continued (e.g., file not found) and (2) something is badly screwed up and I don't know what's broken, HALP! |
14:48:32 | Jehan_ | Araq: It can still be useful to encode complex diagnostic information for a number of reasons, so multiple types for exceptions can make sense (in a statically typed language, that is). |
14:48:44 | Araq | yup |
14:48:48 | OrionPK | dom96 you may want to switch your unit tests to use waitfor instead of runforever |
14:48:54 | OrionPK | so they end w/o interrupt |
14:49:10 | Jehan_ | But generally, you want either a "fail" or "panic" type of exception, and that's that. |
14:49:17 | Araq | however, once you have an exception type that allows for a full stack trace, it's moot |
14:49:44 | Araq | I've yet to see an exception type that encodes more than *that* |
14:50:02 | Araq | so ... you can use this type everywhere and call it a day |
14:50:23 | Araq | it's however much dirtier than subtyping |
14:50:59 | Jehan_ | Araq: The question is, does the elaborate type hierarchy give you anything? |
14:51:04 | Jehan_ | In practice, I mean. |
14:51:34 | Jehan_ | I'd argue that every time you have an exception handler that relies on a subtype of a subtype of the main exception type, something's broken about your system. |
14:51:46 | Araq | well in the compiler we have ERecoverableError for non-local control flow ;-) |
14:52:47 | Araq | I'd argue that exceptions are for non-local control flow and if you pretend you don't need *that*, you don't have an inherently recursive problem |
14:53:02 | dom96 | OrionPK: yeah, I already switched some. |
14:53:10 | OrionPK | dom96 although that looks like a hot loop |
14:53:14 | Jehan_ | Araq: I'll both agree and disagree with you there. |
14:53:48 | Jehan_ | Agreeing in that it's my preference to facilitate this, disagreeing with you in that it's not really necessary (just sometimes very convenient). |
14:54:02 | Araq | it's not a coincidence ML has exceptions |
14:54:06 | dom96 | OrionPK: The loop in waitFor? |
14:54:17 | OrionPK | yeah |
14:54:25 | Araq | and even ML uses subtyping for exceptions |
14:54:44 | Araq | it's not just a broken C++ design |
14:54:56 | OrionPK | dom96 I'd expect CPU to shoot up to 100% while it waits |
14:55:54 | Jehan_ | Araq: ML doesn't use subtyping in that sense. Exceptions in ML are basically an extensible algebraic data type. |
14:56:28 | dom96 | OrionPK: You'd expect it? |
14:56:33 | dom96 | OrionPK: why? |
14:56:43 | dom96 | or do you mean that it does shoot up? |
14:57:18 | dom96 | Anybody here experienced with SSL? |
14:58:48 | Jehan_ | In Talis, I have a `fail` statement, a `try` expression, a `panic` statement, and a `try!` expression. |
14:59:18 | dom96 | Jehan_: What's the difference between `try` and `try!`? |
14:59:27 | Jehan_ | `fail` and `try` work in a sort of Prolog-like fashion, except that `fail` can have an optional payload, error message, and error code. |
14:59:50 | Jehan_ | dom96: try! catches panic calls, try doesn't. |
15:00:08 | dom96 | oh, interesting. |
15:00:10 | Jehan_ | try is an expression that returns an option-like type (closer to Scala's Try[T]) type. |
15:00:49 | Jehan_ | Mostly you'll just use it as a boolean, but you can optionally extract other information from it, if you need it (and assuming "fail" provided a payload). |
15:01:34 | Jehan_ | dom96: It's so that normal try handlers don't have to deal with truly exceptional conditions, but just with normal deviations from expected behavior. |
15:08:22 | * | Sht0 joined #nimrod |
15:10:04 | OrionPK | dom96 because a loop that doesnt do anything will typically eat up cpu cycles |
15:10:50 | dom96 | it calls poll |
15:10:54 | dom96 | poll blocks |
15:11:12 | OrionPK | oh ok |
15:11:33 | OrionPK | dom96 perfect then :) |
15:13:56 | OrionPK | dom96 is there an await for a timer? |
15:14:06 | OrionPK | like Task.Delay |
15:14:08 | dom96 | sleepAsync |
15:14:44 | OrionPK | some good sister functions of WaitFor would be WaitForAll/WaitForAny |
15:15:54 | dom96 | You can do: waitFor fut1 or fut2 |
15:16:15 | dom96 | and similarly you can also use 'and' |
15:17:00 | OrionPK | ah perfect |
15:17:46 | OrionPK | so you could implement a timeout of 100ms with that by doing waitfor taskA or sleepAsync(100) |
15:20:39 | Jehan_ | dom96: What about about arbitrarily large sets? |
15:21:11 | Jehan_ | dom96: Practical use cases for WaitForAny() involve a pretty large number of futures. |
15:23:14 | dom96 | yes |
15:23:40 | dom96 | Jehan_: Ok, we can add it then. |
15:24:01 | NimBot | Araq/Nimrod bigbreak d7d059a Araq [+0 ±16 -0]: more tests green |
15:24:23 | Araq | see you later |
15:24:34 | Jehan_ | A very typical use case is: You start N tasks with greatly varying runtimes, then use WaitForAny() or its equivalent to do postprocessing of results in order of termination. |
15:25:47 | OrionPK | later araq |
15:32:50 | * | Sht0 quit () |
15:33:06 | EXetoC | should the install scripts include the compiler directory? the c2nim package fails because it can't find llstream |
15:59:19 | * | fowl joined #nimrod |
15:59:19 | * | fowl quit (Changing host) |
15:59:19 | * | fowl joined #nimrod |
16:08:17 | * | Varriount-Mobile joined #nimrod |
16:13:48 | * | Varriount-Mobile quit (Ping timeout: 255 seconds) |
16:14:50 | * | untitaker quit (Ping timeout: 250 seconds) |
16:15:32 | * | EXetoC quit (Quit: WeeChat 1.0) |
16:20:11 | * | untitaker joined #nimrod |
16:26:28 | * | EXetoC joined #nimrod |
16:36:03 | * | q66[lap] joined #nimrod |
16:36:27 | * | q66[lap] quit (Changing host) |
16:36:27 | * | q66[lap] joined #nimrod |
16:41:44 | * | vendethiel joined #nimrod |
16:53:49 | * | flaviu joined #nimrod |
16:55:32 | * | mahoganygiraffe quit (Quit: WeeChat 0.4.3) |
16:55:47 | * | woodgiraffe joined #nimrod |
17:04:01 | * | io2 quit (Quit: ...take irc away, what are you? genius, billionaire, playboy, philanthropist) |
17:48:56 | Araq | EXetoC: yes, they should for this reason |
17:53:05 | * | flaviu quit (Remote host closed the connection) |
17:54:08 | * | flaviu joined #nimrod |
17:55:37 | * | flaviu quit (Read error: No route to host) |
17:55:45 | * | flaviu joined #nimrod |
18:01:19 | * | gkoller joined #nimrod |
18:18:01 | OrionPK | dom96 i still cant compile jester |
18:18:37 | Demos | Araq, when I tried to build it I found that the compiler sources were in the config file but that did not work, I had to manually add the directory to the path |
18:18:56 | EXetoC | Demos: works for me |
18:19:39 | EXetoC | is said config file being read? |
18:20:20 | EXetoC | enter some random chars and see if you get any errors |
18:23:27 | EXetoC | or compile manually. jester's output doesn't include read config files |
18:27:06 | OrionPK | not sure if this compiles: https://github.com/dom96/jester/blob/new-async/tests/asynctest.nim |
18:28:02 | OrionPK | ah i see.. works with the 'match' parameter, but I'm not sure where the 'match' symbol comes from |
18:28:45 | * | mko quit (Ping timeout: 240 seconds) |
18:34:37 | dom96 | OrionPK: compile newtest |
18:46:48 | * | Fr4n quit (Ping timeout: 255 seconds) |
18:51:08 | dom96 | I should remove the other tests to remove confusioon |
18:53:34 | * | Fr4n joined #nimrod |
18:53:38 | * | Fr4n quit (Changing host) |
18:53:38 | * | Fr4n joined #nimrod |
18:57:52 | * | kunev quit (Ping timeout: 240 seconds) |
19:01:17 | dom96 | Anyone wanna test Async SSL on Linux for me? |
19:05:51 | def- | dom96: you have a file to run or how? |
19:07:17 | dom96 | def-: try this https://gist.github.com/dom96/d5e8cb3e816e8c80cab7 |
19:07:25 | dom96 | compile with -d:ssl |
19:08:02 | def- | on which branch? |
19:08:44 | dom96 | bigbreak |
19:09:14 | def- | I would have to figure out how to get bigbreak compiled first |
19:09:32 | def- | probably have to bootstrap again? |
19:09:33 | dom96 | the instructions are in the readme |
19:09:36 | dom96 | yes |
19:11:26 | * | Ven joined #nimrod |
19:13:18 | def- | dom96: lib/pure/net.nim(186, 16) Error: value of type 'SslError' has to be discarded |
19:13:33 | dom96 | argh |
19:13:36 | dom96 | ok, let me fix that. |
19:15:22 | NimBot | Araq/Nimrod bigbreak ac01ed5 Dominik Picheta [+0 ±1 -0]: Fix net module on Linux. |
19:15:26 | dom96 | def-: try it now |
19:16:47 | def- | Got response: 200 OK, but it takes 10 seconds |
19:17:06 | def- | (and my ping to github.com is not that high) |
19:17:28 | dom96 | yeah. That's something I will have to fix... |
19:19:54 | dom96 | But at least you get a response eventually. |
19:53:45 | * | kunev joined #nimrod |
20:00:17 | * | kunev quit (Ping timeout: 245 seconds) |
20:07:00 | * | kunev joined #nimrod |
20:10:32 | * | Jehan_ quit (Quit: Leaving) |
20:17:10 | * | kunev quit (Ping timeout: 250 seconds) |
20:28:47 | wan | dom96: I mostly have between 0.2s and 2.0s if I change the url to https://www.google.com. Maybe github's homepage is sometimes slow? |
20:29:01 | wan | Or what do you have to fix? |
20:41:40 | * | filwit joined #nimrod |
20:53:10 | * | Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…) |
20:56:31 | NimBot | Araq/Nimrod bigbreak 41c7cde Araq [+0 ±9 -0]: updated iup.nim; made tests green |
20:56:31 | NimBot | Araq/Nimrod bigbreak d1d7d9e Araq [+0 ±1 -0]: Merge branch 'bigbreak' of https://github.com/Araq/Nimrod into bigbreak |
20:57:03 | Araq | if some of you guys want to help me, please git bisect for sets/tsets2.nim |
20:57:14 | Araq | I'd like to know which commit broke this test |
20:58:15 | * | q66 quit (Quit: Leaving) |
20:58:50 | * | Varriount|Mobile joined #nimrod |
21:00:11 | * | q66 joined #nimrod |
21:01:41 | * | gkoller quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…) |
21:01:58 | filwit | nim/lib/stdlib.nimble ? has babel been official renamed since last I was here? |
21:02:26 | filwit | or has .nimble always been around? |
21:02:52 | Araq | not officially but it's only a fake package anyway |
21:03:01 | Araq | the compiler accepts both .nimble and .babel |
21:03:20 | filwit | cool :) |
21:04:10 | filwit | Araq: I could help you remove the T/P prefixes in the stdlib if you want |
21:04:26 | Araq | lol |
21:04:37 | filwit | Araq: not sure about how to find the bug which broke your test tho |
21:04:41 | Araq | you're too late |
21:04:50 | Araq | check out the bigbreak branch |
21:05:08 | filwit | what? i'm looking at bigbreak right now, and tons of packages still have TFoo everywhere |
21:05:19 | Araq | we already got rid of most of them |
21:05:24 | Araq | like what? |
21:05:40 | filwit | hmm... yeah, i guess it was just the ones i clicked on |
21:05:45 | filwit | actors |
21:06:13 | filwit | i clicked on a couple others, but can't remember |
21:06:33 | filwit | but yeah, i see now a lot has been changed... cool :) nice work |
21:06:59 | wan | What's wrong with tsets2, Araq? It compiles and run on my end (on bigbreak branch) |
21:07:04 | filwit | (ps, i'm retarded... i should be looking at the commits to the right...) |
21:07:53 | filwit | oh... i see, the entire actors module has been depreciated.. nice |
21:12:24 | wan | (I spoke too fast. I had d:release) |
21:12:49 | Araq | wan: well for me it produces wrong C code |
21:14:04 | EXetoC | it's ok no one will notice |
21:23:17 | * | Trustable quit (Quit: Leaving) |
21:42:23 | * | q66[lap] quit (Quit: Textual IRC Client: www.textualapp.com) |
22:27:18 | NimBot | Araq/Nimrod devel 05c1fb0 Erwan Ameil [+0 ±1 -0]: Escape ' and / when using escape in xmltree |
22:27:18 | NimBot | Araq/Nimrod devel 6bd7473 Andreas Rumpf [+0 ±1 -0]: Merge pull request #1510 from idlewan/xml_escape... 2 more lines |
22:27:37 | NimBot | Araq/Nimrod devel 7dac395 Erwan Ameil [+0 ±0 -2]: Remove outdated ZeroMQ example (zmq has been moved out of the stdlib) |
22:27:37 | NimBot | Araq/Nimrod devel cb9f669 Andreas Rumpf [+0 ±0 -2]: Merge pull request #1508 from idlewan/zmq... 2 more lines |
22:28:20 | NimBot | Araq/Nimrod devel a249a12 Erwan Ameil [+0 ±1 -0]: Secure and HttpOnly cookies |
22:28:20 | NimBot | Araq/Nimrod devel 1c85a49 Andreas Rumpf [+0 ±1 -0]: Merge pull request #1509 from idlewan/cookies... 2 more lines |
22:28:22 | * | q66[lap] joined #nimrod |
22:28:42 | * | q66[lap] quit (Changing host) |
22:28:42 | * | q66[lap] joined #nimrod |
22:29:58 | * | clone1018__ is now known as oldclone |
22:31:42 | * | clone1018 joined #nimrod |
22:32:35 | wan | I have your bisect answer |
22:33:00 | wan | 90e3c99baec7204bd5d6aba423bc0ffa5a97392b is the first bad commit |
22:33:13 | wan | Adds TSet.isValid(). Jul 26 |
22:34:14 | Araq | but I commented out this and it still fails |
22:34:26 | Araq | maybe it never worked on windows in the first place, for some reason? |
22:38:32 | * | untitaker quit (Ping timeout: 245 seconds) |
22:39:07 | * | woodgiraffe quit (Quit: WeeChat 0.4.3) |
22:42:13 | wan | dunno about windows, but that's from where it begins misgeneratin the asserts |
22:42:30 | wan | I'; on linux |
22:44:07 | Araq | hmm ok then |
22:44:26 | Araq | well it triggers a compiler bug, so I might as well fix that instead |
22:45:00 | Araq | makes me wonder though if anybody actually tests his PRs |
22:45:33 | Araq | or if the people who apply PRs ever check nimbuild's test results |
22:47:07 | Triplefox | Safe assumption is that nobody tests anything, or tests it well enough |
22:47:08 | wan | Well, in this case, nothing is triggered if you compile with -d:release |
22:52:40 | Araq | hu indeed, it does |
22:53:07 | Araq | so it really is the asserts, interesting |
22:54:16 | Araq | good night |
22:56:56 | wan | good night |
23:00:10 | * | untitaker joined #nimrod |
23:06:41 | * | BlaXpirit quit (Quit: Quit Konversation) |
23:19:39 | * | Matthias247 quit (Read error: Connection reset by peer) |
23:23:18 | * | Demos quit (Read error: Connection reset by peer) |
23:36:02 | * | flaviu quit (Ping timeout: 245 seconds) |
23:36:35 | * | darkf joined #nimrod |
23:55:06 | * | q66 quit (Ping timeout: 260 seconds) |
23:56:15 | * | q66 joined #nimrod |