<< 02-02-2015 >>

00:00:17*BlaXpirit quit (Quit: Quit Konversation)
00:05:28dom96reactormonk: I'd rather not make Nimble complex
00:06:41reactormonkdom96, how about split each wrapper library into two parts - one that's the pure interface wrapper, no actual nim code, which carries the upstream version number, and another one which depends on it?
00:07:26reactormonkthat way you can theoretically mix & match and nimble stays simple
00:12:19*Matthias247 quit (Read error: Connection reset by peer)
00:21:34flaviudom96: What about 1.2.* and 1.*.* ?
00:22:25flaviuI mean as a nimble version specifier.
01:03:56flaviugokr_: Dead link on http://goran.krampe.se/2014/10/29/nim-and-oo/ around UPDATE: See part IV about this
01:04:20*davidhq quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
01:19:31*EXetoC quit (Quit: WeeChat 1.1.1)
01:39:28*Trustable quit (Quit: Leaving)
01:39:30*davidhq joined #nim
01:42:47*davidhq quit (Client Quit)
01:50:24*davidhq joined #nim
01:56:29*davidhq quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
02:16:47DemosI would say a seperate package for each ABI break in the library
02:32:24*darkf joined #nim
02:35:23*bmaxa joined #nim
02:48:53*Demon_Fox quit (Ping timeout: 246 seconds)
02:59:36*Demon_Fox joined #nim
03:10:11*superfunc[mobile quit (Quit: Connection closed for inactivity)
03:16:04flaviuhttp://rigaux.org/language-study/syntax-across-languages/ should come in handy for "but x does things this way" arguments ;)
03:24:33*d3m1gd quit (Ping timeout: 265 seconds)
03:36:51*BitPuffin quit (Ping timeout: 246 seconds)
03:56:06*ehaliewicz quit (Ping timeout: 246 seconds)
04:05:28*Varriount_ joined #nim
04:07:37*Varriount quit (Ping timeout: 255 seconds)
05:15:41*BitPuffin joined #nim
05:21:52*BitPuffin quit (Ping timeout: 255 seconds)
05:25:28*johnsoft quit (Ping timeout: 255 seconds)
05:45:34*fizzbooze joined #nim
06:13:17*gsingh93 joined #nim
06:16:39*kapil__ joined #nim
06:26:37*fizzbooze quit (Quit: WeeChat 1.1.1)
06:55:32*VinceAddons joined #nim
07:15:21*gokr joined #nim
07:16:51*gokr_ quit (Ping timeout: 264 seconds)
07:18:15reactormonkdef-, I think you killed the tests you have before
07:19:16*Demon_Fox quit (Quit: Leaving)
07:25:09*BitPuffin joined #nim
07:25:55*bjz joined #nim
07:28:57*JinShil joined #nim
07:29:03*bjz quit (Client Quit)
07:29:41*BitPuffin quit (Ping timeout: 250 seconds)
07:39:06*gokr quit (Quit: IRC for Sailfish 0.8)
07:46:32*bjz joined #nim
08:13:19*DemonOne quit (Ping timeout: 250 seconds)
08:18:04*BitPuffin joined #nim
08:22:51*BitPuffin quit (Ping timeout: 264 seconds)
08:27:18*Trustable joined #nim
08:27:53*gXen joined #nim
08:37:55*DemonOne joined #nim
08:42:50*gokr joined #nim
08:42:54*gXen left #nim (#nim)
08:48:16*VinceAddons quit (Read error: Connection reset by peer)
08:49:46*d3m1gd joined #nim
08:54:25*d3m1gd quit (Ping timeout: 264 seconds)
08:58:09*JinShil quit (Quit: Konversation terminated!)
09:03:36*sillesta joined #nim
09:09:47*Netfeed joined #nim
09:16:46*DemonOne quit (Ping timeout: 245 seconds)
09:45:02*dumdum joined #nim
09:51:42*grom358 joined #nim
09:51:56grom358i have only just heard of this language
09:52:06grom358how is nim's GC suitable for games?
10:05:48def-grom358: it's high performance, only runs when you allocate new data (so you can just avoid allocating data) and you can set when it may run and for how long: http://nim-lang.org/gc.html
10:22:21*d3m1gd joined #nim
10:27:31*gsingh93 quit (Quit: Connection closed for inactivity)
10:28:16*gXen joined #nim
10:31:46ekarlsoAraq: did you fix the code generator bug you said ?
10:41:23reactormonkekarlso, is the issue closed?
10:41:58ekarlsoreactormonk: I dunno, he just said there was a codgen bug that was the issue that I was seeing
10:46:20reactormonkekarlso, github issues are our kind of bureaucracy
10:48:02reactormonkekarlso, probably the best way to get it fixed is to make a test for the compiler tests/ directory
10:49:30reactormonkekarlso, find anything? https://github.com/Araq/Nim/commits/devel
10:50:05ekarlsonot even sure where to look at that list :p
10:50:22ekarlsosorry to say I'm not that familiar with the compiler stuff ;)
10:50:45ekarlsohttps://bpaste.net/show/dcdbf12f0084
10:56:33ekarlsou got a clue reactormonk ?
11:28:02*MajorWork joined #nim
11:28:36*chemist69 joined #nim
11:41:57ekarlsooh well :p
11:42:03ekarlsoI'll wait for a fix then
11:53:36*akiradeveloper joined #nim
11:54:03akiradeveloperhow can I do formatted printing? couldn't find printf
11:55:18akiradevelopershould always use logging module?
12:01:04dumdumakiradeveloper: maybe this: http://nim-lang.org/strutils.html#%,string,openArray[string]
12:02:38akiradeveloperoh thanks. it's pythonistic
12:12:35*Jehan_ joined #nim
12:15:49*kashyap_ quit (Quit: Page closed)
12:16:12*kashyap_ joined #nim
12:17:05kashyap_A quick question about javascript interop. How can I write code that generates window.alert("hello")? I am able to generate just alert("hello") by declaring proc with importc
12:20:48*kapil__ quit (Quit: Connection closed for inactivity)
12:26:58*BitPuffin joined #nim
12:31:07Jehan_kashyap_: {.importc: "window.alert".} should work for that.
12:31:11*dumdum quit (Ping timeout: 256 seconds)
12:31:35*BitPuffin quit (Ping timeout: 250 seconds)
12:31:37ekarlsoAraq: please ping when the codegen bug is fixed :p
12:31:46kashyap_thanks Jehan_
12:32:14Jehan_kashyap_: No promises, but basically, the code generator does just a textual insertion for this.
12:33:17kashyap_ Error: invalid pragma: importc: "window.alert"
12:35:01*gXen quit ()
12:41:39Jehan_kashyap_: Huh. What's the exact code? It should be something like: proc alert(s: cstring) {.importc: "window.alert".}
12:44:15*dumdum joined #nim
12:55:11*Jehan_ quit (Remote host closed the connection)
12:55:45*Jehan_ joined #nim
13:00:23*akiradeveloper quit (Remote host closed the connection)
13:11:19*gunn quit (Ping timeout: 265 seconds)
13:19:16*gunn joined #nim
13:32:32*kapil__ joined #nim
13:35:47*dumdum quit (Ping timeout: 256 seconds)
13:43:02*darkf quit (Quit: Leaving)
13:46:37*akiradeveloper joined #nim
13:49:01*johnsoft joined #nim
13:54:46DanjclaI'm looking at the c2nim code and there isn't ./configure / a makefile / instructions / etc. Should I just try to compile stuff one by one, or is there something to do that's obvious if one has been using nim for a while? https://github.com/nim-lang/c2nim
13:55:18*davidhq joined #nim
14:00:12*bmaxa quit (Quit: Leaving)
14:01:11def-Danjcla: in Nim we generally use "nimble install" to install something. should work with nimble, but requires the nim compiler from git. nimble itself has instructions for how to install it: https://github.com/nim-lang/nimble
14:05:45akiradeveloperI want to release a resource on SIGINT. possible with try-finally? It doesn't work. I suppose it doesn't catch SIGINT as exception
14:07:31DanjclaSweet, that worked (and nimble is pretty). Thanks! Off to play with C++ integration...
14:08:26def-akiradeveloper: you probably have to write your own signal handler that throws an exception (i hope that works). as a starting point C like signal handling should be possible with the posix module
14:09:51def-Danjcla: any idea where nimble should have been mentioned so that you would've known this already? In the tutorial?
14:10:34akiradeveloperdef-, really? how cumbersome...
14:11:32def-akiradeveloper: i guess because signals work so differently on platforms. if you get it working, maybe it can go into the standard library?
14:12:47akiradeveloperdef-, anyway I will try
14:13:28akiradeveloperI need more elegant way for loan pattern.
14:14:02def-akiradeveloper: wait, SIGINT was ctrl-c, wasn't it..
14:14:08def-that actually causes an exception
14:14:21akiradeveloperyes, ctrl-c
14:14:41akiradeveloperwhat? so my finally clause actually works?
14:14:49def-Sorry for the confusion
14:15:03akiradeveloperwhich is correct?
14:15:50akiradeveloperyeah, code will tell
14:16:23def-The SIGINT is handled, but doesn't seem to throw an exception
14:16:43*MyMind joined #nim
14:17:31akiradeveloperI see
14:17:47akiradeveloperso that's correct my finally doesn't work actually
14:17:56def-Easy to fix though
14:18:14*dumdum joined #nim
14:18:27def-akiradeveloper: https://gist.github.com/def-/b52fa7a01d9b021873bb
14:18:42*Sembei quit (Ping timeout: 272 seconds)
14:18:52akiradeveloperI need something like this http://rustbyexample.com/drop.html
14:21:01akiradeveloperWhat is setControlCHook?
14:21:29def-it sets the proc to be called when a ctrl-c is received
14:22:00akiradeveloperdefined in os module?
14:22:11def-system module i believe
14:22:17akiradeveloperI see
14:22:18def-sleep is from os
14:23:59akiradeveloperI want to sweep the resource when the wrapping object is gc-ed
14:24:32akiradeveloperAdd some behavior when the object is gc'd...
14:24:35gokrDanjcla: You might want to read my article on c2nim "Nim Wrapping C" (or any of the others): http://goran.krampe.se/category/nim/
14:24:58def-akiradeveloper: a destructor? http://nim-lang.org/manual.html#destructors
14:25:21def-(not sure what they do with GCed stuff)
14:27:12akiradeveloperwhen the program is killed, GC sweep all objects in heap?
14:27:24gokrDanjcla: There was another article recently on wrapping C libs, but... I can't recall where it is
14:27:26akiradeveloperI guess no
14:27:44Jehan_akiradeveloper: signal handlers are very fragile things. Many system calls cannot be safely called from signal handlers and doing funky things with the stack (such as throwing exceptions) is generally a bad idea.
14:27:55Danjclagokr: Thanks, that looks super-useful! I want to use C++ APIs, but I assume that's similar.
14:28:06Jehan_akiradeveloper: No, the GC doesn't do that, that would be unnecessary overhead.
14:28:26gokrDanjcla: For C++ you should check with Araq since he is putting quite a lot of work into c2nim for that right now.
14:28:37akiradeveloperI see
14:29:25Jehan_Imagine, for example, a large program that did swap out most of the memory. The GC would then have to page all of that back in before being allowed to terminate.
14:29:48akiradeveloperyes
14:30:21Danjclagokr: I did, he gave me a pointer, a doc in the devel tree, but not that much detail; but I'm guessing your stuff will give me a feel for things, and then the doc he pointed to will make more sense. https://github.com/Araq/Nim/blob/devel/doc/nimc.txt ImportCpp pragma
14:30:27akiradeveloperI am looking for a nice way to free some resource when the program is killed
14:31:23akiradeveloperIf I shouldn't throw exception on SIGINT what else can we do to do that?
14:31:46Jehan_akiradeveloper: use addQuitProc() (which is basically an atexit() wrapper).
14:32:20Jehan_akiradeveloper: The clean (but cumbersome) way to do advanced signal handling is to dedicate a separate thread to it.
14:33:15Jehan_It's a bit tedious, because once you start with multiple threads, you have to worry about signals being delivered to the correct thread.
14:33:46akiradeveloperaddQuitProc looks good
14:35:51Jehan_Note that addQuitProc()/atexit() functions won't be called when the process is terminated by a signal.
14:39:41Jehan_The basic problem with using a signal handler directly is that signals can interrupt the program at pretty much any time, including in the middle of an operation, where you may then be operating on undefined state.
14:40:05Jehan_Hence, most signal handlers just set a variable that is then checked by the program or you use a multithreaded solution.
14:40:16*gunn quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
14:40:42akiradeveloperaddQuitProc won't be called when terminated by signal?
14:40:48Jehan_No, it won't.
14:41:19Jehan_That's just how the OS works. A signal that terminates a process will terminate the process without sending any notification.
14:41:59Jehan_The process thus can't even know it's being terminated before it dies.
14:42:49Jehan_Hence, when you intercept SIGINT, you have to do the termination part yourself.
14:46:00*BitPuffin joined #nim
14:57:52Danjclagokr: Did the next post regarding impure intermediary libraries and make test green / declaring victory happen? Haven't been able to find so far.
14:59:16gokrNah, didn't do any more posts yet
14:59:30*VinceAddons joined #nim
15:00:34akiradevelopervery very weird code is made https://github.com/akiradeveloper/nim-fuse/blob/develop/session.nim you see setControlCHook in mount proc
15:01:29akiradeveloperI am still looking for an elegant way to release resources when the program is terminated for some reason
15:02:07Danjclagokr: Than I shall search for impurity elsewhere :)
15:07:53*akiradeveloper quit (Ping timeout: 245 seconds)
15:10:19dumdumproc takeproc(fn: proc(x: int): int) , 'x' seems unncessary ie it should be easy for nim to accept; proc takeproc(fn: proc(int): int) ..no? (less stuff to type for programmer)
15:14:24dumdummaybe even drop 'proc' and accept: fn: (int): int
15:16:38Araqdumdum: *shrug* usually parameter names are for documentation. you seem to want '->' from the future module
15:20:57dumdum'->' yes, exactly! thanks
15:22:15ekarlsoAraq: did you get a fix for the codegen bug ?
15:22:29Araqekarlso: no
15:22:43ekarlsoAraq: boo :P
15:22:44Araqmaybe I will be able to look into it tonight
15:23:52*Jehan_ quit (Quit: Leaving)
15:25:07ekarlsoAraq: would be awesome
15:25:45*gunn joined #nim
15:28:00dom96ekarlso: it seems to only happen for long URLs
15:28:07dom96you might be able to workaround it temporarily
15:28:10dom96if you're just testing
15:28:30ekarlsodom96: how ?
15:29:16dom96shorten the url
15:29:41ekarlsodom96: meh, not possible really with nimble
15:29:48ekarlsosince it's searcing for multiple tags at once
15:30:05dom96work on different functionality :)
15:30:23ekarlsodom96: meh, rest is already working in nimble :P
15:30:29ekarlsosearch / list / install
15:30:31ekarlsotowards registry
15:31:16*saml joined #nim
15:33:18ekarlsodom96: what else to do ? :D
15:33:28dom96let me test it?
15:33:44ekarlsosure, i'll post up a branch to my gh
15:39:03*JohnReginald joined #nim
15:39:22*JohnReginald left #nim ("Leaving")
15:46:25d3m1gdis there a pragma to mark a procedure being protected from dead code elimination?
15:47:05*gunn quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
15:53:49Araqd3m1gd: exportc does that
15:55:08d3m1gdAraq: oh, neat, thanks
15:58:41*Angry_ joined #nim
16:06:16*mytrile joined #nim
16:10:11Araqhi Angry_ welcome. I hope your name doesn't reflect your mood
16:10:19Araqhi mytrile welcome
16:10:34Angry_Not at all.
16:10:38mytrileHey Araq
16:11:50Angry_Just hanging out about to start my first nim project. Since people are talking how strait forward is it to interface with c++ classes?
16:16:09*saml quit (Quit: Leaving)
16:18:10Araqdepends on the C++ that is actually used
16:18:26Araqbut support for it improved quite a bit, yeah
16:18:54*saml joined #nim
16:19:33*BlaXpirit joined #nim
16:19:53*EXetoC joined #nim
16:20:51Angry_Araq: does the easy to use part include calling methods on c++ classes that I have full source code to?
16:21:03ekarlsodom96: hmm
16:21:12ekarlsoso echoPackageVersions currently goes out to github
16:21:17AraqAngry_: yeah
16:21:37ekarlsocould we make it support registry and github I guess ?
16:23:28dom96ekarlso: yes.
16:23:30dom96I can do that.
16:23:42dom96All you need to do is expose a packages.json file.
16:23:54ekarlsodom96: it doesn't have one
16:24:00ekarlsoregistry is /pacakges/<id>/releases
16:24:04dom96ekarlso: you need to generate one
16:24:08ekarlso:/
16:24:51ekarlsodom96: the way I did it atm was to make nimble use the api
16:25:53ekarlsodom96: https://nim-pkg.svcs.io/api-docs
16:26:41ekarlsothough I guess it wouldn't be that hard to make a new endpoint
16:26:41dom96But you're generating it here: https://nim-pkg.svcs.io/packages
16:26:47dom96That's what I want :)
16:26:58ekarlsodom96: but that doesn't include releases ;P
16:27:13dom96also it's a slightly different format
16:27:18dom96You just need to adjust it slightly
16:27:48dom96but hrm
16:27:58samlthat url doesn't work for me
16:28:25dom96Perhaps it does make more sense to not grab a list of all the packages
16:28:42dom96As long as you do it cleanly in Nimble then I have no problem with it.
16:29:01ekarlsosaml:
16:29:04ekarlsohow you mean ?
16:29:11ekarlsoit's running in norway atm
16:29:13samlThis server could not prove that it is svcs.io; its security certificate is from www.cloudistic.net. This may be an attacker intercepting your connection.
16:29:45ekarlsoyeah, that's my bad haha
16:29:46samldon't use https://
16:30:14ekarlsoideally it should be packages.nim-lang.org ;p
16:31:21ekarlsodom96: I dunno if it's bad to have to do GET /packages/<id>/releases to get releases also
16:32:58dom96I would just include them in the output for /packages/<id>
16:33:02dom96unless you have a reason not to do that
16:33:07dom96I need to go. Bbl.
16:33:16ekarlsodom96: meh, rest api's and all that :p
16:33:34ekarlsodom96: u'd just grab /packages then the versions for the ones u need
16:52:17*Danjcla left #nim ("WeeChat 1.1")
16:53:12*Danjcla joined #nim
16:53:22*Varriount|Busy joined #nim
16:56:04Varriount|Busyreactormonk: One of your recent PR's broke builds for Windows.
16:56:11*superfunc joined #nim
16:56:50Varriount|Busyreactormonk: http://buildbot.nim-lang.org/builders/windows-x32-builder/builds/120
16:57:43superfunchey everyone
16:57:52Varriount|BusyI've no idea why it only affects Windows builds. Nothing in your commits looks to be Windows- or Linux-specific
16:58:02Varriount|Busysuperfunc: Hi!
17:01:33superfuncI'm gonna try to see about getting that typedef added in BSD to fix building; I already put in a patch for csources to build.
17:02:09superfuncbasically, BSD defines some type u_int32_t whereas most things look for uint32_t
17:02:10Varriount|Busydef-: I think your commits are responsible too.
17:04:55*chemist69 left #nim (#nim)
17:17:21*brson joined #nim
17:21:23*superfunc quit (Quit: leaving)
17:35:36*gmpreussner|work quit (Read error: Connection reset by peer)
17:35:43*gmpreussner|work joined #nim
17:39:58*Matthias247 joined #nim
17:56:47*gmpreussner|work quit (Ping timeout: 244 seconds)
17:56:57*MajorWork quit (Quit: Leaving)
18:01:04*BitPuffin quit (Ping timeout: 245 seconds)
18:03:53*mytrile1 joined #nim
18:06:33*mytrile quit (Ping timeout: 252 seconds)
18:10:04*sampwing joined #nim
18:16:42*Danjcla quit (Quit: WeeChat 1.1)
18:29:13*UberLambda joined #nim
18:42:01*gsingh93 joined #nim
18:43:22*superfunc joined #nim
18:44:10def-Varriount|Busy: i don't understand how my commits cause this: http://buildbot.nim-lang.org/builders/windows-x32-builder/builds/120/steps/Bootstrap%20Debug%20Version%20of%20Nim%20Compiler%20(With%20C%20Backend)/logs/stdio
18:44:40def-1. Those commits didn't change algorithm.nim and 2. all changes were OS-independent
18:59:20*dapz joined #nim
19:05:31*threewood quit (Ping timeout: 245 seconds)
19:09:31*dapz quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
19:10:45reactormonkVarriount|Busy, >:)
19:11:14reactormonkVarriount|Busy, got a windows VM somewhere for me to do some regression testing?
19:11:47*threewood joined #nim
19:11:57*gmpreussner|work joined #nim
19:13:35reactormonkVarriount|Busy, from what I see, my only commit is the merge-commit
19:13:50def-reactormonk: yeah, rest are my commits, but I don't have windows either
19:14:00def-i looked through all commits, can't see anything that causes this
19:14:03reactormonktime for some piratebay?
19:14:27reactormonkHm, no windows image anymore
19:25:31onionhammerwhats wrong w/ windows?
19:25:34onionhammernot working?
19:25:35onionhammeron devel?
19:29:27def-onionhammer: yes, bootstrap seems to fail after my commits
19:29:40def-according to the builder
19:29:57dumdumhttps://www.modern.ie/en-us/virtualization-tools lets you download a windows vm
19:30:31dumdumbut not sure of its limitations
19:35:53Angry_irrc they deactivate after a set amount of time
19:47:31*dumdum quit (Ping timeout: 256 seconds)
19:49:04*BlaXpirit quit (Quit: Quit Konversation)
19:50:49*BlaXpirit joined #nim
19:59:07*mwbrown joined #nim
19:59:25*Angry_ quit (Read error: Connection reset by peer)
20:10:22mwbrownIs there any way to specify array sizes at object construction time? For instance, define an object with "size" and have something like myArray : array[0..size, int]
20:10:35mwbrownto get size safety on a dynamic object
20:11:43mwbrownSpecifically I'm trying to create an object with a nested array of ints, so array[0..height, array[0..width, int]]
20:12:15EXetoCT:static[int], which is experimental
20:13:52EXetoCyou could also try T:range and then array[T, int]
20:14:29mwbrownthe array size will only be known at runtime, unfortunately
20:15:48mwbrownalthough it doesn't look like there is an explicit constructor support for objects, instead relegating that to helper functions that call "new" and return the reference after doing necessary setup
20:17:55EXetoCthen you must use a seq instead
20:18:25EXetoCconstructor as in T(field1: x, field2: y)?
20:19:07mwbrownT(width: int, height: int)
20:19:09EXetoCand if T is a reference type then 'new' will be invoked automatically
20:19:53EXetoCbut usually you'd to want to wrap your constructors in procs
20:22:39mwbrownalright, in that case is there a way I can preallocate a seq to be of a certain size?
20:23:32mwbrownI have a seq[seq[int]] and I want to make the outer one from 0..height and the inner one from 0..width
20:24:12EXetoCnewSeq[T](len: int)
20:25:08EXetoCI wonder if calling setLen afterwards preserves the capacity
20:25:13*bjz quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
20:27:24EXetoCwhich is the size of the internal buffer (the length is always <= the capacity). if you set the *length* then you must keep track of how much has been intialized
20:27:27EXetoCperhaps it's obvious
20:31:51mwbrownlooks like it's working, I had an off-by-one error because of the range syntax but otherwise I think I've got it
20:32:40mwbrownhttp://pastebin.com/zBEb6x1q
20:33:19mwbrownthat code is working unless there is a better way to initialize a seq[seq] other than a for loop for the inner sequence
20:35:17EXetoCthere are no such shortcuts
20:36:53EXetoCyou can just use a single sequence of chars if the lengths are supposed to be uniform, but then you need to think about how to index it
20:37:33mwbrownright, you can always flatten a 2D array into a regular array. I was just trying different ways out in Nim
20:38:04*FusionGaming quit (Ping timeout: 255 seconds)
20:42:20*FusionGaming joined #nim
20:43:38*UberLambda quit (Quit: Leaving the Matrix)
20:43:55*UberLambda joined #nim
20:44:18*Varriount|Busy quit (Quit: Page closed)
20:47:45*FusionGaming quit (Ping timeout: 250 seconds)
20:55:05*bjz joined #nim
20:56:02*chemist69 joined #nim
20:57:35ekarlso.eval @[1,2] & @[3,4]
20:57:38Mimbusekarlso: eval.nim(3, 7) Error: value of type 'seq[int]' has to be discarded
20:58:25*bjz quit (Read error: Connection reset by peer)
20:58:52*UberLambda quit (Quit: Leaving the Matrix)
20:58:52*FusionGaming joined #nim
20:58:54*bjz joined #nim
21:00:41*bjz quit (Client Quit)
21:04:09*dapz joined #nim
21:06:20*brson quit (Quit: leaving)
21:06:27*brson joined #nim
21:06:57*sampwing quit (Ping timeout: 252 seconds)
21:08:40*dapz quit (Ping timeout: 255 seconds)
21:09:56ekarlsodom96: around ? :D
21:10:03ekarlsohttps://github.com/ekarlso/nimble
21:10:05ekarlsoinitial
21:11:55*bjz joined #nim
21:13:57*mytrile1 left #nim (#nim)
21:14:52*bjz quit (Client Quit)
21:15:01*superfunc quit (Ping timeout: 252 seconds)
21:23:03*chemist69 quit (Quit: leaving)
21:28:08*Etheco joined #nim
21:32:28*nande joined #nim
21:37:42*DemonOne joined #nim
22:03:31*grom358 quit (Remote host closed the connection)
22:06:51*sampwing joined #nim
22:16:40*Demon_Fox joined #nim
22:20:13*dtscode quit (Quit: (dtscode.io))
22:21:22*dts|pokeball joined #nim
22:56:23*mwbrown quit (Ping timeout: 246 seconds)
22:59:34*Trustable quit (Quit: Leaving)
23:11:04*Demon_Fox quit (Ping timeout: 255 seconds)
23:19:19*sampwing quit (Ping timeout: 252 seconds)
23:20:03*sampwing joined #nim
23:22:40*Angry joined #nim
23:26:15*sillesta quit (Ping timeout: 256 seconds)
23:56:07*davidhq quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)