<< 21-04-2015 >>

00:05:44transfuturistwhat should i use in place of a word type?
00:05:53transfuturistunsigned?
00:07:07transfuturistwell, no, that still wouldn't let me use streams with unsigned types
00:07:19transfuturistthe unsigned separation is a pain.
00:08:06transfuturistah, read() is generic, good
00:31:10*vendethiel quit (Ping timeout: 272 seconds)
00:46:52*banister quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
00:47:36*banister joined #nim
00:48:39*BitPuffin quit (Ping timeout: 256 seconds)
01:05:27*gmpreussner|lapt quit (Quit: Leaving)
01:07:59*askatasuna joined #nim
01:09:45*filwit quit (Quit: Leaving)
01:13:53*pregressive joined #nim
01:18:25*pregressive quit (Ping timeout: 255 seconds)
01:30:35transfuturist.eval var a: seq[int] = nil
01:31:10transfuturist> >
01:31:15transfuturistwhere's mimbus?
01:35:00transfuturistAraq: do you think you could add a sugar for object refs?
01:35:11transfuturistso you can do type Foo = ref object ...
01:35:21transfuturistinstead of making two types for each
01:36:12transfuturistwait, that already seems to work
01:36:35TriplefoxThat's the preferred style now, i think
01:43:04*saml_ quit (Remote host closed the connection)
01:48:34*adam| is now known as adam12
01:49:44*noob_ joined #nim
01:50:12noob_Hey can anyone tell me how I could dereference an object through an argument for a procedure?
01:50:34def-noob_: obj[] or what do you mean?
01:52:11noob_well I've defined an object, lets call it screen. Screen has values xPos, and yPos. I'm passing it into a function like so add( addr screenObj )
01:52:35noob_how can I dereference screenObj in add, so that I can get dynamic values for xPos and yPos
01:52:43def-noob_: any reason you pass it as a ptr?
01:52:54noob_Mostly because I'm unsure on how to use it dynamically
01:53:20noob_Because I'm pretty sure arguments are static values
01:53:22noob_right?
01:53:31def-do you want to manipulate the passed object? then make it "proc add(x: var Screen) = ..."
01:53:40noob_Ohh
01:53:43noob_Gotcha
01:53:46noob_Didn't know that was legal
01:54:02TriplefoxYou could do it the c way but it's not really idiomatic
01:54:18def-a ptr would work as well, but it's unsafe and bad style, and you have to manually dereference with screenObj[] in some places
01:54:57renesacand there is the "ref" keyword in the middle
01:55:47noob_So I can just pass it into add like so : add(screenObj)
01:56:00def-noob_: right
01:56:01renesacyes
01:56:10renesacor screenObj.add()
01:56:54renesacwith or w/o the parenthesis (but as you are making a change, I advise the parenthesis to indicate that an action is being made, not just an field access)
01:57:34noob_I'm getting an illegal capture.
01:57:52def-noob_: what does your full code look like?
01:58:01noob_proc makeScreen*( obj: var screen, canvas: proc() ): proc() =
01:58:12noob_makeScreen(panel, drwFunc)
01:58:23noob_where panel is a screen
01:58:44noob_more specifically its a var panel = screen
01:59:15def-hm, don't understand the error. Have a paste?
01:59:49def-ah, you're returning a proc that uses obj
02:00:04def-that's not legal because obj may not exist anymore, while the proc may still exist
02:00:15def-so it would write into wrong memory
02:00:52noob_Gotcha
02:01:14noob_What would you suggest?
02:01:44def-Not sure what you're trying to do. Making screen a ref type might work, then you don't need the var anymore
02:03:11noob_Essentially I'm just drawing a 3D/2D panel, and then rotate it around
02:03:36noob_But Yea, you got me the tools to figure out the problem
02:03:37noob_Cheers
02:03:40noob_I appreciate it
02:03:58def-I'm not sure why makeScreen returns a proc
02:04:15noob_It has to do with our current drawing implementation
02:04:20noob_its a bit rudementary
02:04:36noob_Essentially it just loops through a sequence of procedures
02:04:39noob_and calls them
02:05:24renesacand now is my turn: https://gist.github.com/ReneSac/912219fbf0cfc87f4440
02:05:45renesacwhy the procs/iterators that return "var T" arent working?
02:06:08renesac(they are commented out)
02:06:15*anthony_ quit (Quit: My Mac has gone to sleep. ZZZzzz…)
02:06:52renesacthe compiler gives the rather unhelpfull message: seqviews.nim(111, 15) Error: identifier expected, but found ''
02:07:40def-renesac: pass in a var SeqView[T] and don't yield a var
02:07:48def-don't yield a ref* i mean
02:09:04renesacindeed, that fixes the mitems
02:09:23renesacbut what is wrong with the [] that returns a var T?
02:09:29renesacI can't overload it that way?
02:10:15def-should work in devel, let's see
02:10:55def-it works with a return s.data[s.base + x]
02:11:25def-may be a compiler bug/limitation
02:11:39renesacoh
02:11:46renesacit is because I call a template first
02:12:03def-right, but without the var return type it works, which seems inconsistent
02:12:18renesacyeah, it is strange
02:17:37def-I would suggest to use implicit return value (without result or return) with one liners only, easier to understand
02:18:29renesacright
02:18:34renesacfor the most part I do it
02:21:30renesacnow everything looks to be working right
02:21:44renesacthanks
02:23:27*leonlee joined #nim
02:25:44*Kingsquee quit (Quit: Konversation terminated!)
02:27:43*gsingh93 quit (Ping timeout: 244 seconds)
02:29:34*anthony joined #nim
02:29:57*anthony is now known as Guest76077
02:31:03*askatasuna quit (Quit: WeeChat 1.1.1)
02:34:37*wb quit (Ping timeout: 264 seconds)
02:40:15*egrep joined #nim
02:40:16*darkf joined #nim
02:40:29*vendethiel joined #nim
02:43:22*Demon_Fox quit (Ping timeout: 265 seconds)
02:43:59*pregressive joined #nim
02:44:53dhasenanHuh, so apparently if you want to wrap a constructor for a templated C++ class in Nim, the importcpp argument you need to provide is "'0(@)".
02:44:56dhasenanThat's...strange.
02:45:36renesacit's araq that invented this syntax
02:46:00renesacwhat would you preffer instead?
02:46:24dhasenanWell, from other usages, it looks like '0 indicates the first template parameter in the current context.
02:46:55dhasenanSo I should have something like: proc constructPODVector[T] {.importcpp: "Urho3D::PODVector<'0>(@)".}
02:47:26dhasenan(Adding in arg list and so forth.)
02:47:35renesacwell, you should talk with Araq about that...
02:47:41dhasenanI'll file a ticket.
02:48:56*Demon_Fox joined #nim
02:53:20fowlmouthdhasenan, what is the question
02:57:04*Kingsquee joined #nim
02:59:13fowlmouthhttps://github.com/Araq/Nim/blob/6fb372d96bade748aa6cb3484fef2118b4585f26/doc/nimc.txt#L457
02:59:19*Demon_Fox quit (Ping timeout: 265 seconds)
02:59:24*brson quit (Quit: leaving)
03:03:50dhasenanfowlmouth: the question is https://github.com/Araq/Nim/issues/2578
03:03:56dhasenanIt's not a question, just an observation.
03:05:42*vendethiel quit (Ping timeout: 272 seconds)
03:07:04fowlmouthimportcpp: "'0(@)"
03:07:50fowlmouthoh
03:07:52dhasenanRight.
03:08:13dhasenanAnd there doesn't appear to be a way to wrap `template <typename T> int foo(T)`.
03:08:20dhasenanFortunately, I don't need to do that right now.
03:08:53fowlmouthhhh
03:12:02fowlmouthdhasenan, got it
03:12:19fowlmouththe return type is '0
03:13:24dhasenanOh. So you can't wrap `template <typename T> int foo(Bar<T>)`
03:14:08fowlmouthyes. that would be proc foo [x] (some:x): int {.importcpp:"foo<'1>(@)", nodecl.}
03:15:37dhasenanNope.
03:15:54dhasenanThat would wrap `template <typename T> int foo(T)`.
03:16:15fowlmouthok
03:16:26fowlmouth? lol
03:17:24fowlmouthpity i dont have all day to sit here and write code for free
03:17:45dhasenanI'm not asking you to.
03:23:11fowlmouthi think importcpp is messed up
03:23:36dhasenanSometimes, yes. But the basics work.
03:37:43fowlmouthdhasenan, you should reopen that issue, it is a bug
03:37:58fowlmouthhere the difference is between 'argument' and 'parameter' https://github.com/Araq/Nim/blob/6fb372d96bade748aa6cb3484fef2118b4585f26/doc/nimc.txt#L457
03:42:51dhasenanfowlmouth: templates don't have return types, so that doesn't make much sense.
03:43:17dhasenanIt looks like a breaking but intended change in behavior.
03:43:21fowlmouthdhasenan, templates aren't relevant here
03:43:46fowlmouthyou're frustrating. i'm out
03:47:06*pregressive quit (Remote host closed the connection)
03:54:20*gsingh93 joined #nim
03:55:28*ChrisMAN quit (Ping timeout: 255 seconds)
04:06:50*Guest76077 quit (Quit: My Mac has gone to sleep. ZZZzzz…)
04:10:17*transfuturist quit (Quit: Lost terminal)
04:32:56*johnsoft quit (Ping timeout: 240 seconds)
04:34:01*johnsoft joined #nim
04:46:42*gsingh93 quit (Ping timeout: 244 seconds)
04:47:18*anthony joined #nim
04:47:41*anthony is now known as Guest46751
04:50:23*transfuturist joined #nim
04:54:15transfuturistdoes nim not have libraries to handle non-UTF8 unicode?
04:54:43tstmDoes nim handle utf8 variable names?
04:54:55tstmeg. emoticons and such
04:55:19transfuturisti'm talking about sequences of unicode as a type, not variable names
04:55:42tstmYeah, I got it. But it just reminded me of something I wanted to ask some time ago. :P
04:56:24tstmFor your question, I don't know. UTF16 and such are pretty important to support database things etc.
04:56:54transfuturistmaybe bindings to iconv will work
04:58:29transfuturistspeaking of bindings to desirable features, i'm wondering if using a c library for coroutines would work for nim, like libconcurrency
05:01:44transfuturistprobably not...
05:18:06transfuturistah, iconv seems to be abandoned...
05:19:48transfuturistthe changelog is 5 years old, ick
05:20:07transfuturistlet's try it straight from the source
05:20:10transfuturisthttp://site.icu-project.org/download
05:25:37*vendethiel joined #nim
05:33:19*a5i quit (Quit: Connection closed for inactivity)
05:37:07*Guest46751 quit (Quit: My Mac has gone to sleep. ZZZzzz…)
05:43:06*anthony joined #nim
05:43:30*anthony is now known as Guest34916
05:44:00Araqtransfuturist: we have encodings.nim in the stdlib already
05:46:34*johnsoft quit (Ping timeout: 272 seconds)
05:46:52*johnsoft joined #nim
05:50:42*wb joined #nim
05:51:06*leonlee quit (Quit: Leaving)
05:51:18*smelod joined #nim
05:53:32*vendethiel quit (Ping timeout: 272 seconds)
05:54:06Araqdhasenan: I can see no breaking changes
05:54:44Araqthe proc types are used because -- guess what -- we don't have the list of generic types at this stage in the compiler anymore
05:55:43Araqfowlmouth: proc p(param: int) = ...
05:55:46Araqp(arg)
05:56:03Araqthat's the difference. arg is what you pass, param is the formal parameter
06:02:00*gsingh93 joined #nim
06:09:10*gokr quit (Quit: Leaving.)
06:11:21*BlaXpirit joined #nim
06:25:24*OnO joined #nim
06:27:19*Guest34916 quit (Ping timeout: 245 seconds)
06:27:33reactormonkAraq, need some different format from nimsuggest, can I just parse the compiler output via writelnHook?
06:27:57Araqomg, no
06:28:10Araqyou *can* do that, but it's insane
06:28:27Araqjust patch compiler/suggest.nim instead
06:28:33reactormonkYes, I know it's insane.
06:29:14Araqwe like to have a --json switch so everything the compiler emits is in json format
06:29:23Araqwould that help you?
06:29:49reactormonkKinda, but it's not json since emacs doesn't have a native lib for that and elisp is slooooow and linking code to emacs... bleh
06:31:17transfuturist>emacs
06:31:20reactormonkthe protocol needs to know the full message because the first for bytes are the message size, so I need to have all suggesting in a seq - could I rewrite the suggestX stuff to return their suggestings instead?
06:31:34reactormonktransfuturist, they're working on it/stallman
06:31:37*endragor joined #nim
06:33:21Araqhrm I see
06:33:44Araqso you would simply emit the 4 bytes length before the message in the writelnHook?
06:36:40reactormonknope, I need to compile the full answer. the protocol is question - response. So question would be "suggest names at X with dirtyfile Y" and the answer needs to be the full list at once
06:36:57reactormonkI can't send incrementally.
06:37:50Araqok
06:38:06Araqyou need to override the hook for that, but you don't need to parse things then
06:38:25Araqyou need to patch nimsuggest.nim
06:39:00*vendethiel joined #nim
06:39:46Araqjust add a couple of lines for emacs support to the serve() proc and implement an --emacs command line option
06:40:17Araqhacking support into it for specific editors is valid, that's why we split it from the main compiler
06:40:49*dhasenan__ quit (Remote host closed the connection)
06:42:36reactormonkso basically remove suggestWriteln(symToStr(....)) and rename it to suggestSym() and either print it or yield it to the hook? can I go break apis?
06:43:27Araqyou don't have to change any of that, everything goes via the hook already
06:44:40reactormonkyes, but the information is in string form in the hook already
06:45:20AraqI thought you only need to concat these strings in your hook implementation and then output length+concatened stuff
06:46:08reactormonkthen you'd have (answer . ("suggest ...." "suggest ....")) and would have to parse it on the emacs side?
06:46:24Araqbut yes, you can also change the API as long as the protocol remains the same
06:46:35Araqit's not a public API
06:47:03reactormonkok, I'll go do that instead. Should also make --json easier since you only have to package the object
06:47:33Araqmake a proper PR because code review
06:47:33reactormonkneed to go sleep, o/
06:47:37reactormonksure
06:47:40Araqok bye
06:53:43*cmk_zzz_ joined #nim
07:04:01*transfuturist quit (Ping timeout: 264 seconds)
07:07:48*endragor_ joined #nim
07:09:54*endragor quit (Ping timeout: 246 seconds)
07:12:24*thotypous quit (Ping timeout: 244 seconds)
07:14:24*cmk_zzz_ quit (Ping timeout: 245 seconds)
07:15:55*thotypous joined #nim
07:17:03*vendethiel quit (Ping timeout: 245 seconds)
07:19:55*endragor_ quit (Remote host closed the connection)
07:24:05*untitaker quit (Ping timeout: 248 seconds)
07:26:06*untitaker joined #nim
07:26:51*cmk_zzz_ joined #nim
07:37:50*bcinman quit (Quit: My Mac has gone to sleep. ZZZzzz…)
07:44:44*vendethiel joined #nim
07:45:56*Trustable joined #nim
07:55:34*bjz joined #nim
07:59:34*bjz quit (Client Quit)
08:00:00*bjz joined #nim
08:05:37*HakanD_ joined #nim
08:06:13*bjz quit (Ping timeout: 248 seconds)
08:07:30*coffeepot joined #nim
08:09:42*vendethiel quit (Ping timeout: 272 seconds)
08:11:04*gsingh93 quit (Ping timeout: 256 seconds)
08:11:27*jeffburdges joined #nim
08:14:13*zahary1 joined #nim
08:14:48*endragor joined #nim
08:14:51*zahary quit (Read error: Connection reset by peer)
08:19:23*superfunc joined #nim
08:24:46*Pisuke joined #nim
08:37:54*vendethiel joined #nim
08:42:58*superfunc quit (Quit: Page closed)
08:44:22*smelod quit (Ping timeout: 244 seconds)
08:45:10*bjz joined #nim
08:50:58*Demon_Fox joined #nim
08:59:53*gokr joined #nim
09:00:56*vendethiel quit (Ping timeout: 240 seconds)
09:01:58*jeffburdges quit (Quit: jeffburdges)
09:05:00OnOhi
09:05:31Araqhey
09:05:39OnOAraq: regarding this column numbering, to you just want getColNumber to return starting with 0
09:05:48OnObut is it okay diagnostics to start with 1 ?
09:06:06Araqno, diagnostics need to start with 0 too
09:06:28Araq1. this is documented and important for idetools
09:06:35Araq2. IMHO it makes more sense anyway
09:07:34Araqcolumns are "between" the characters, so they should start at 0.
09:08:56OnOouch, but editors such as emacs expect 1 to be first column?
09:09:41OnOeven Visual Studio starts column with 1
09:09:47Araqdunno, Aporia starts with 0
09:10:23def-oooh, that explains why the column output of nim always seemed wrong by 1!
09:10:37Araq-.-
09:11:17def-I think most editors start line and column numbers with 1
09:11:23OnOand yes! Python dianostics start with 1 too!
09:11:51Araqugh, so yet another thing we have to change for consistency with stupidity
09:12:35repaxFor error messages meant to be read by people I prefer visual feedback over column numbers, i.e:
09:12:37repaxSyntax error here: ------^
09:13:48Araqat least it's consistent with line numbering then
09:13:52*Araq sighs
09:14:33OnOindeed
09:16:19OnOrepax: adding this is another step for user friendly diagnostics
09:17:27repaxOnO: Clang is a good inspiration. It can even mark column intervals
09:17:52Araqrepax: we can do the --------^ too but I forgot which command line switch enables it
09:18:12repaxOh, nice. I didn't know
09:20:01OnOtemplate optPrintSurroundingSrc*: expr =
09:20:02OnO gVerbosity >= 2
09:20:24HakanD_fwiw, sublime text also starts from 1
09:21:17Araqstrange. it's as if programmers suddenly cannot count from 0 anymore :P
09:21:50HakanD_i've also wandered why the column no is always one off, assumed it's buggy and stopped using the column no all together (:
09:22:34OnOhonestly I think Nim should internally count from 0, but just output diagnostics from 1
09:22:37OnOjust when printing
09:22:38Araqno, it's not buggy :P it's correct when everybody else is wrong
09:22:45AraqOnO: yup, make it happen please
09:22:51HakanD_(:
09:22:54cmk_zzz_as long as it is consistent I wouldn't care
09:23:06OnObut it is now all f.. up, lines start with 1 (internally), column from 0
09:24:00AraqOnO: making it consistent internally is too much work
09:24:14HakanD_well, theoretically it's correct, not sure about practicality
09:24:31Araqquite some stuff depends on line, col numbers internally
09:25:14OnOso hey, I will just remove change to getColNumber but add +1 to lexMessage family?
09:25:26Araqyes
09:25:41Araqand patch Aporia too then ;-)
09:30:56Araqyou also need to patch a couple of places in msgs.nim
09:34:36*TEttinger quit (Ping timeout: 264 seconds)
09:36:54*gokr quit (Ping timeout: 250 seconds)
09:37:11OnOupdated https://github.com/Araq/Nim/pull/2566 see 1st commit
09:38:00OnOI just patched liMessage
09:38:34OnOseems everything else calls that
09:41:36OnOas for Aporia, I am on OSX, but "Since Aporia uses gtk, and gtk is not easy to compile natively under MacOSX (yet)"
09:42:58Araqyou don't have to run Aporia, just patch it and let us review and merge it
09:44:02OnOokie, let me try
09:55:21OnOhttps://github.com/nim-lang/Aporia/pull/82
09:57:19BlaXpiritAraq, I can replace isMainModule with defined(testing)
09:57:35BlaXpiritbut how to change the tester for this?
09:57:54Araqyou can grep for isMainModule in the tester
09:58:04Araqit's a primitive implementation
09:58:18BlaXpiritah i see testStdlib
09:58:37AraqBlaXpirit: btw I tested the new pcre and can confirm it just works on windows too
09:59:02BlaXpiritAraq, but it may not work with some features
09:59:10BlaXpiritdll should be updated
10:01:36BlaXpiritnah, I can't make sense of the testing code
10:01:47BlaXpiritanother problem i have is how to actually define testing
10:01:58BlaXpiritand also I don't see why the code is not run
10:02:10BlaXpiritit looks like it's supposed to run the executable
10:02:47Araqthere is a cmd const you can update so that -d:testing is always passed
10:04:32BlaXpiritok ok but i still don't know why it isn't actually run
10:05:09Araqyou need to fake the TSpec into a runnable test
10:05:41Araqneeds more patches I guess :P
10:05:47BlaXpiritmaybe it's best that you just do it
10:06:07*arnetheduck joined #nim
10:06:17Araqwell but you can update the isMainModule usages in the stdlib
10:06:21BlaXpirityes
10:06:27Araqok great
10:06:44BlaXpiritwould also need to drop broken stuff
10:06:58BlaXpiritsome isMainModule should stay
10:07:43Araqexactly
10:10:03*vendethiel joined #nim
10:11:20BlaXpirithttps://github.com/Araq/Nim/blame/devel/lib/pure/pegs.nimfix ???
10:12:13AraqI think we can remove that file by now
10:12:49Araqnimfix doesn't work anyway, for some reason
10:13:32*Kingsquee is now known as flopsquid
10:17:10BlaXpiritAraq, a little problem.
10:17:15BlaXpiritevery imported module is tested
10:17:48def-when isMainModule and defined(testing): ?
10:18:01BlaXpirit i suppose ...
10:18:22BlaXpiritbut no
10:18:24Araqhrm?
10:18:33BlaXpiriti run actors.nim -d:testing
10:18:39BlaXpiritand got a failing test in times.nim
10:19:04Araqaye, def-'s suggestion is a good one?
10:19:04BlaXpiritdef-, problem with that is, when isMainModule blocks will still be run
10:19:18BlaXpiriti'm leaving some isMainModule blocks as they were
10:21:07BlaXpiritdifferent approach: leave testing in isMainModule
10:21:27BlaXpiritbut change non-test blocks to when not defined(testing) and isMainModule
10:21:43Araqthat's a good idea too
10:21:56Araqthere should only be a few of these
10:28:20*wb quit (Ping timeout: 265 seconds)
10:30:25*Ven joined #nim
10:32:52*vendethiel quit (Ping timeout: 244 seconds)
10:36:04*vendethiel joined #nim
10:46:27*HakanD_ quit (Quit: Be back later ...)
10:46:35*BitPuffin joined #nim
10:46:40*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
10:46:54*gokr_ quit (Ping timeout: 245 seconds)
10:46:56*HakanD_ joined #nim
10:51:04*jfchevrette joined #nim
10:51:04*HakanD_ quit (Ping timeout: 245 seconds)
10:51:12*Ven joined #nim
10:55:40BlaXpiritlooks like romans is broken
10:55:45BlaXpiritcan i fix it in the same pull request
10:55:55BlaXpiritreally dont wanna make mant of them
10:55:58BlaXpiritmany
10:56:22Araqthrow it out of the stdlib ?
10:56:30Araqwhy does the stdlib need roman numbers?
10:56:51BlaXpiritit's cool lol
10:57:12BlaXpirityou wrote it yourself
10:57:17Araqthis should be a nimble package
10:57:30BlaXpiritmake it so, but later
10:57:34BlaXpiritfor now i'll just fix it
10:57:38Araqwell no, I adapted it years ago. ok.
10:57:48AraqI didn't write the original code I think
10:58:01BlaXpiritsays (c) Copyright 2011 Philippe Lhoste
10:59:42Araqthat's not my name
11:00:02BlaXpiritoh yeah, i didnt mean it as confirmation
11:00:08AraqI don't even know how to speak Lh
11:00:17BlaXpiritfirst i looked that it was committed by you
11:00:21BlaXpiritthen saw this
11:00:57Araqproc decimalToRoman*(number: range[1..3_999]): string lol
11:01:18Araqthe romans could only count until 3999
11:01:29Araqno wonder they needed slaves for everything
11:02:18BlaXpiritCan there be `echo` in testing code?
11:02:25BlaXpiritwill it output during testing phase?
11:02:41Araqwell kind of
11:02:51Araqthe tester compares this against the given spec
11:02:59BlaXpiritjust asking if i need to wrap every echo in when not defined(testing):
11:03:03Araqbut there is no spec section for stdlib modules
11:03:20Araqyou need to transform the echos into asserts
11:03:44BlaXpiritthat's a different task
11:03:57Araqthat's a necessary task
11:04:30*cmk_zzz_ quit (Ping timeout: 276 seconds)
11:05:10*wb joined #nim
11:10:45BlaXpirittimes has a test that takes year out of range[-10_000..10_000]
11:10:59BlaXpiritand it's intentional
11:11:56BlaXpiriti mean it intentionally wants to get # Fri 7 Jun 19:20:45 BST 30143 but year range is too small
11:12:29BlaXpiritI don't see any point in this arbitrary range anyway
11:12:50Araqarbitrary boundaries is the nature of computing
11:13:28Araqbut I guess we can make 'year = int'
11:13:42BlaXpirithttps://github.com/Araq/Nim/commit/4fbba0a#diff-91d68bf578ea4bbef60621e73245f542L114
11:14:33BlaXpirittimes module was not tested since 8 Jul 2012 lol
11:14:57Araqbbs
11:21:24*vendethiel quit (Ping timeout: 264 seconds)
11:25:03*vendethiel joined #nim
11:30:46*jefus joined #nim
11:41:18*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
11:46:39*flopsquid quit (Quit: Konversation terminated!)
11:47:06*OnO quit (Quit: My iMac has gone to sleep. ZZZzzz…)
11:48:48*Senketsu joined #nim
11:49:47*Ven joined #nim
12:00:25*BitPuffin quit (Remote host closed the connection)
12:10:40BlaXpirithardcoded mimetypes? okaay
12:10:50BlaXpiritwho's gonna maintain it? nobody?
12:25:39BlaXpiritstrutils formatSize is broken
12:25:39*zahary1 quit (Read error: Connection reset by peer)
12:34:21*HakanD_ joined #nim
12:35:12*banister quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
12:36:25*vendethiel quit (Ping timeout: 256 seconds)
12:42:51*vendethiel joined #nim
12:43:14*HakanD__ joined #nim
12:47:12*HakanD_ quit (Ping timeout: 264 seconds)
12:52:53*mpthrapp joined #nim
12:56:17*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
13:03:53*Ven joined #nim
13:04:27*vendethiel quit (Ping timeout: 265 seconds)
13:07:33AraqBlaXpirit: what's the alternative? some bloated mimetype library that only works on unix and reads crap from /etc/bananajoe?
13:07:51BlaXpiritat least some good way to maintain it
13:08:35Araqwhat's your definition of "maintain"? add every mimetype under the sun?
13:08:52BlaXpiritfor example, where were the current mimetypes taken from?
13:09:03Araqif a new important mimetype comes along, somebody will create a PR
13:09:42BlaXpiritthat is ridiculous
13:09:54BlaXpirit"having only old mimetypes and ones that someone needed"
13:10:06Araqwhy? this way the module stays lean and useful
13:10:25*devzerp quit (Ping timeout: 256 seconds)
13:10:25*no_name quit (Ping timeout: 256 seconds)
13:10:31Araq"having thousands of crapware bloating everything that wants mimetype support"
13:10:45BlaXpiritwut
13:11:30BlaXpiriti assume it was stolen from here http://cpansearch.perl.org/src/RRWO/Media-Type-Simple-v0.30.6/share/mime.types
13:12:00BlaXpiritor maybe they stole from the same place
13:12:20Araqwell you can make it read some file at compile-time if you feel like it
13:12:41BlaXpiritthat's exactly what i wanted
13:18:28Araq*shrug* having to add 3 lines of code per decade has hardly anything to do with maintenance
13:19:17BlaXpiritAraq, the point is not how many lines you would add
13:19:25BlaXpiritbut how you would detect what and when to add!!!
13:19:39Araqsomebody who actually needs it will tell you.
13:20:30*vendethiel joined #nim
13:20:46Araqit's the same with time: who cares if the stdlib's time doesn't support the Maya calendar?
13:21:35*pregressive joined #nim
13:21:36BlaXpiritno
13:21:51BlaXpiritwhatever, pointless arguing with you
13:22:34*pregressive quit (Remote host closed the connection)
13:22:54*jfchevrette quit (Quit: Textual IRC Client: www.textualapp.com)
13:31:28*Varriount|Busy joined #nim
13:33:01Varriount|BusyWhen writing a binary literal, why is '0b1000000000000000' (0b + 16 digits) invalid for a 16-bit integer?
13:34:25BlaXpiritVarriount|Busy, isn't that 1 more than
13:34:48BlaXpiritno
13:35:02BlaXpiritah, it is
13:35:15BlaXpirit0b1000000000000000 < 1<<15 - False
13:38:24Varriount|BusyBlaXpirit: Huh?
13:39:26BlaXpiritVarriount|Busy, let me put it this way
13:39:28BlaXpirit0b1000000000000000 > int16.high
13:40:16BlaXpirit0b111111111111111 == int16.high
13:41:07*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
13:41:27*vendethiel quit (Ping timeout: 244 seconds)
13:41:31Varriount|BusyBlaXpirit: But isn't that only 15 bits?
13:41:45BlaXpiritVarriount|Busy, it is
13:41:51BlaXpirit1 bit is for sign
13:42:05AraqVarriount|Busy: use uint16 'u16
13:42:14Varriount|BusyAh, Ok.
13:42:53Varriount|BusyI was under the expectation that the binary notation would include the sign bit.
13:42:58*no_name joined #nim
13:42:59*devzerp joined #nim
13:43:14BlaXpiriti don't think it ever does
13:45:03*vendethiel joined #nim
13:45:35Varriount|Busyno_name, devzerp: You're the same person?
13:45:42Varriount|BusyAlso, Hi.
13:47:14*noob_ quit (Quit: Page closed)
13:53:16*Ven joined #nim
13:54:09*HakanD__ quit (Quit: Be back later ...)
13:54:36*HakanD__ joined #nim
13:55:13Varriount|BusyAraq: So, my final project in my CS course for this semester is to write an interpreter.
13:55:41Araqfor what?
13:56:07Varriount|BusyAraq: Nothin in particular. We're supposed to model a simplified processor.
13:56:11Varriount|Busy*Nothing
13:56:41BlaXpiritoh that's fun. once i made a mediocre asm interpreter
13:57:19Varriount|BusyI currently have 31 opcodes. Nim's 'enum' mechanism is proving very useful.
13:59:24BlaXpiritturning opcodes into binary and then interpreting the binary would be horrible though
13:59:25Araqmake it process a subset of Nim ;-)
13:59:28BlaXpiriti hope that is not what u have to do
13:59:48BlaXpiritwhat i meant to say: turning commands into binary and then interpreting the binary would be horrible though
14:00:01AraqBlaXpirit: that's not horrible at all
14:00:52AraqVarriount|Busy: if you want advice: don't model a stack machine
14:01:03Araqdesign a register based machine
14:01:23thotypousunless you plan to run forth in the machine :)
14:02:32Araqin my not so humble opinion register based machines are much easier
14:04:46Varriount|BusyAraq: Well, the layout is very simple. One register, 4096 * 16 bytes of memory, no flags, etc.
14:05:18renesacVarriount|Busy: I just opened a bug related to that, I should add binary notation too
14:05:21renesachttps://github.com/Araq/Nim/issues/2539
14:05:51renesacsee the alternatives I copied there
14:06:23Varriount|BusyGotta go, Calculus class calls.
14:06:27*Varriount|Busy quit (Quit: Page closed)
14:09:55*vendethiel quit (Ping timeout: 256 seconds)
14:10:46Araqrenesac: The following should work:
14:10:48Araqlet foo: int8 = 0xFF
14:10:49AraqEr no. why?
14:11:34Araq0xff is obviously 255.
14:11:40thotypousand int8 is signed
14:11:43thotypousso out of range
14:11:56*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
14:11:58*justicefries joined #nim
14:12:21renesacwell, the reason why I think this is in the title: Hex literals should represent bit-patterns, not numbers.
14:12:43Araqthat ignores the problem though
14:12:54Araqyou need to give it a *type*
14:13:20Araqand let foo: typeHere = nowGuessTypeFromHereProperly is not part of the language
14:14:04BlaXpiritliterals should be literals
14:14:22BlaXpirituntil the last possible moment
14:14:33renesacyeah, it should be some "bitpattern" convertible to the "typeHere"
14:14:39thotypousthat depends if you assume the literal to be unsigned and cast it to signed when reaching the int8 declaration
14:15:02thotypousIMHO the default for literals should be signed
14:15:13BlaXpiritwut
14:15:14thotypousbecause that is the convention in nim
14:15:28BlaXpiritno language has this
14:15:32thotypousTest.java:3: error: incompatible types: possible lossy conversion from int to byte
14:15:34thotypous byte n = 0xff;
14:15:36BlaXpiritwhat are you even talking about
14:15:43*jeffburdges joined #nim
14:15:57BlaXpiritthotypous, it is a signed byte, isnt it
14:15:59AraqBlaXpirit: "no language has this" continues to be a non-argument.
14:16:20Araqwe all know where to find Java and C++.
14:16:31*pregressive joined #nim
14:16:46Araq(which amusingly don't agree on this point at all)
14:17:26thotypousjava agrees with nim because it only has signed integers
14:17:33thotypouswhich is the default in nim
14:17:38thotypousbut C++ doesn't
14:18:30BlaXpiritoh well, i don't remember a language that got integer literals right
14:18:52BlaXpirita language that doesn't have built in long arithmetics, anyway
14:19:17Araqbignums don't help for hexadecimal literals
14:19:33renesacwell, when one writes 0b1000000000000000 he is not thinking on the number behind this, but on the bit pattern
14:19:39BlaXpiriti'm not trying to bring bignum into this topic
14:19:41renesacwell, arguably one should use uints for that
14:19:59renesacbut it is so incredibly ankward to use them in nim that people avoid it
14:20:08Araqthat's good :P
14:20:09renesaceven for those obvious things
14:20:09BlaXpiritjust that python got integer literals right but it doesn't count
14:20:12*johnsoft quit (Ping timeout: 272 seconds)
14:20:14renesacAraq: that is bad
14:20:15renesac:P
14:20:20*johnsoft joined #nim
14:21:02*Ven joined #nim
14:21:58thotypousthen nim could have bit pattern literals like verilog :P
14:22:14thotypous16'b1000_1011_1001_1011
14:24:33thotypousAraq: in nim-lang.org/tut2.html, "Macros have to be implemented in pure Nim code if the foreign function interface (FFI) is not enabled in the compiler" seems to imply there is some option to enable FFI at compile-time, but i couldn't find anything related in koch options, did i misunderstood?
14:25:10renesacthotypous: it is simply not supported
14:25:22*vendethiel joined #nim
14:25:32renesacI think it used to be an option...
14:25:36BlaXpiritconfusing wording
14:26:04Araqthotypous: no, it used to be supported via some define
14:26:29thotypoushmm so that's the reason the REPL outputs messages like "lib/system.nim(2285, 6) Error: cannot 'importc' variable at compile time"?
14:26:38BlaXpirityes
14:26:50thotypousthanks for the clarification
14:26:59fowlmouthi thought the repl was taken out behind the shed and shot already?
14:27:03BlaXpiritthe REPL is barely usable btw
14:27:15thotypousis the support for FFI at compile-time supposed to return at some point?
14:27:29Araqthe REPL is not documented anymore, but 'nim i' still exists
14:27:50thotypous(and also the REPL)
14:28:08Araqthotypous: not in its current form
14:28:25Araqthere are thoughts of how to use TinyC to get a real REPL
14:28:59Araqand instead of compile-time FFI I'm working on a compiler plugin system
14:29:11BlaXpirit:/
14:29:36Araqand there is always staticExec anyway
14:30:25BlaXpiritAraq, remember i was talking about macros, templates and found out about quote
14:30:53BlaXpiritwhat would be nice is if something like quote also supported control statements like https://gist.github.com/7e4a445f5c64ef658d2d
14:32:01BlaXpiritalthough it may even be impossible for a changing value, who knows
14:32:04Araqversion 1 out and reasonable stable would be nicer though
14:32:14BlaXpirityah
14:32:32Araqyou can do it already anyway
14:32:40BlaXpiritdo what
14:32:44Araqyou think 'quote' is a builtin because it's magic
14:32:52Araqbut it's only builtin to be faster
14:33:07Araqyou can have your Nimception already
14:33:16BlaXpiriti know how to implement quote
14:33:16Araqyou only need to implement it as a module
14:33:45Araqgood
14:33:46BlaXpiritand I know how to implement compiletime string templates like i did here https://github.com/BlaXpirit/nimception/blob/master/nimception.nim
14:33:57BlaXpiritbut i don't know how to make a combination of these
14:35:18fowlmouthyou can stack macros
14:35:41BlaXpiritI kinda did
14:35:43fowlmouthhold on ill make an example
14:36:25BlaXpiritin the example I turn a string into code which outputs a string which is then executed
14:37:24*arnetheduck quit (Remote host closed the connection)
14:38:49*untitaker quit (Ping timeout: 256 seconds)
14:39:38*untitaker joined #nim
14:41:52*ingsoc joined #nim
14:42:08ingsocwow, quite a crowd
14:43:06ingsocthe googlesphere is pretty thin on nim
14:43:53*untitaker quit (Ping timeout: 250 seconds)
14:44:12BlaXpiritso thin that it is rarely worth searching for anything outside site:nim-lang.org
14:44:23ingsocI was wondering if there is some light weight concurrency features or libs planned
14:44:37ingsocbig like go channels
14:44:40ingsocbit*
14:44:51BlaXpirita lot of talk goes into this
14:45:39*untitaker joined #nim
14:45:53fowlmouthnim doesnt exist
14:45:56fowlmouthjust ask wikipedia
14:46:30ingsocBlaXpirit: if this can be done while providing seamless multicore utilisation then I predict massive pythonista adoption (with a lil help from establishing an active marketing department for nim)
14:46:49ingsocthis would then drive library support
14:46:51federico2any suggested test framework?
14:46:58BlaXpiritfederico2, unittest of course
14:47:32*banister joined #nim
14:47:38*banister quit (Max SendQ exceeded)
14:47:56federico2ingsoc: why the multicore bit?
14:48:04*vendethiel quit (Ping timeout: 272 seconds)
14:48:23fowlmouthanybody who voted keep on the AFD discussion is canvassing
14:48:46*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
14:48:46*justicefries quit (Quit: My Mac has gone to sleep. ZZZzzz…)
14:48:49BlaXpiritfederico2, https://github.com/flaviut/nre/blob/master/test/init.nim :3
14:50:43federico2BlaXpirit: anything to do functional/integration testing as well?
14:51:01ingsocfederico2: because that is where things are headed HW wise, and it is a buzzword to pique interest, and also because a number of alternative of dynamic languages have fundamental designs that limit the ability to scale without extra work, and also becuase some of the other performant languages like ocaml also have a bad story regarding multi-core (afaict)
14:51:06BlaXpiritfederico2, what's that
14:51:18BlaXpiritwhat's "functional" anyway
14:51:25BlaXpiritintegration i can guess
14:51:49*vendethiel joined #nim
14:52:17ingsoca channels library able to utililise multicore in a sane way would rock
14:52:29ingsocor am i alone in this ?
14:52:31ingsoc:)
14:52:37*untitaker quit (Ping timeout: 264 seconds)
14:53:13BlaXpiritping me when u answer
14:53:20ingsocgo seems to have more ceremony than go, has larger exe's and supports fewer platforms and is maybe slower
14:53:30ingsoci mean more ceremony than NIM
14:53:39*untitaker joined #nim
14:54:16dom96and has no generics
14:54:19dom96no macros
14:54:29dom96no indentation based syntax
14:54:33*banister joined #nim
14:54:51ingsocdom96: yeah wordier, and I am not sure about c integration for go ?
14:55:01ingsochow seamless it is ?
14:55:03ingsocor not
14:55:08dom96good question
14:55:11dom96no idea
14:55:16BlaXpiritthere is not a single thing that go is the best at.
14:55:17dom96but I bet it's worse than Nim's beautiful C ffi :P
14:55:26ingsocdom96: it can;t be nicer
14:55:45ingsoc(I have not used Nim in anger yet I only just found it be it looks the real deal
14:56:08ingsoci was gonna jump on the rust bandwagon as it has become API stable
14:56:12ingsocnot so sure now
14:57:07Araqingsoc: we have TChannel which is a bit ugly, but works
14:58:38federico2ingsoc: I would choose a fast Python over a GIL-free Python any day. Unfortunately many people want buzzwords and shiny features
14:59:31federico2BlaXpirit: what is functional testing in general? Anything with a bigger scope than unit testing and that interact with external components (e.g. filesystem, databases...) but is run in a testbed
14:59:38ingsocfederico2: given that choice of course. That doesn't mean wanting it is a buzzword or not possible
15:00:05ingsochow can wanting to be able to utilize HW in a sane way a buzzword
15:00:14ingsocbe a buzzword*
15:00:16ingsoc: /
15:00:20def-one of the nice things about go is that you don't need forward declarations, even among different files
15:00:46federico2well of course - if I didn't have to choose
15:01:25ingsocfederico2: i was just highlighting the issues with alternatives and where things like go are picking up users
15:01:41*Ven joined #nim
15:03:31federico2ingsoc: I would imagine many Python devs giving Nim a try after being told "it's like Python but GIL-free" expecting a similar OO model and running away in panic :)
15:04:41ingsocfederico2: probably a proportion will run away, but then if thje blogosphere is anything to go by they are going to go which is arguably even more different
15:07:14fowlmouthingsoc, nim's metaprogramming makes things possible that is only possible with compiler support in go
15:07:43fowlmouthi wrote a macro so that import_repo github.com/blah/blah works for ex
15:11:59fowlmouththats the killer feature imo
15:12:32ingsocfowlmouth: my interest in this is that if there is a language out there that enables similar productivity possibilities of slow dynamic languages like python/ruby etc. then this could be a huge win for high performance and data centres as the cost is increasingly coming down to power requirements needed to run your stack verses the cost to build and maintain the code, so if you could build in similar time and use 1/10th the HW then
15:13:06*darkf quit (Quit: Leaving)
15:13:38*bcinman joined #nim
15:13:38*bcinman quit (Client Quit)
15:14:40*vendethiel quit (Ping timeout: 272 seconds)
15:15:08coffeepotspeaking of concurrency, does anyone use nim's "disjoint check" for parallel code? Seems like a nice feature for parallelism
15:15:44ingsocfowlmouth: interesting re. macros, will have to have a look at Nim in more depth
15:16:18Araqcoffeepot: it's still very "experimental" but I think some people out there use it :-)
15:16:39coffeepotit seems amazing, but I never see it mentioned - even on here! :D
15:17:28ingsoclock free multi-threading ?
15:17:55ingsochow can this be with all the time and investment moving into things like STM
15:17:57ingsocetc.
15:19:00Araqingsoc: well it's limited. but I still think it's a solid basis for *safe* GPU programming
15:21:03renesacI tried implementing a type of sipmle slices (I called it views) with minimum low level fidling, but I get that gc error:
15:21:06renesachttps://gist.github.com/ReneSac/912219fbf0cfc87f4440
15:21:19renesacthe test and error are at the end
15:23:00Araqrenesac: well @[1, 2, 3] is put into a const section, it doesn't start on the heap
15:23:04*banister quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
15:23:22Araqso you cannot take it over to your stuff
15:23:39Araqyou need to overload by AST constraints
15:23:55Araqand even then it's fragile
15:24:10Araqthere is a reason why shallowCopy is unsafe ;-)
15:25:09renesacyeah, there is a reason
15:25:20renesacthe system manual also teases at this, but don't explains it
15:25:55Araqmake your view take a 'var seq'. This is safe to "capture"
15:26:15renesacthe string is also put at the const section?
15:26:21Araqyes
15:26:30renesacI tried to force it on the heap, but wasn't successful
15:26:34renesacwill try the var seq
15:27:30renesacin the end, I discovered that I wanted the same magic of OpenArray, but with the ability of limiting the range and working with strings
15:30:44renesacok, now I get a nice compilation error for "var testDirect = view(@[1,2,3,4,5,6,7,8,9])"
15:30:52renesacbut I still get the same runtime error for strings
15:33:21renesacgist updated
15:35:27*banister joined #nim
15:48:38*vince quit (Disconnected by services)
15:49:17*vinnie joined #nim
15:54:57*TEttinger joined #nim
15:55:52*ChrisMAN joined #nim
15:56:41*vendethiel joined #nim
16:12:35*coffeepot quit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
16:20:33*OnO joined #nim
16:31:26*brson joined #nim
16:41:24*gsingh93 joined #nim
16:50:57*dhasenan left #nim (#nim)
16:59:41*TylerE_ is now known as TylerE
17:03:35*BlaXpirit_ joined #nim
17:04:11*vendethiel quit (Ping timeout: 265 seconds)
17:06:10*BlaXpirit_ quit (Client Quit)
17:06:31*BlaXpirit_ joined #nim
17:06:42*BlaXpirit quit (Ping timeout: 250 seconds)
17:06:55*pregressive quit (Remote host closed the connection)
17:12:13*jeffburdges left #nim (#nim)
17:23:28*vendethiel joined #nim
17:43:00*banister quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
17:52:55*bougyman joined #nim
17:53:22bougymanis this an ok place to ask nimble questions?
17:53:40*pregressive joined #nim
17:55:35*HakanD___ joined #nim
17:58:36*HakanD__ quit (Ping timeout: 240 seconds)
18:00:18*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:02:01def-bougyman: sure
18:02:43*smelod joined #nim
18:06:15*endragor quit (Ping timeout: 250 seconds)
18:07:36*Pisuke quit (Ping timeout: 264 seconds)
18:07:56bougymandef-: basically https://github.com/nim-lang/nimble/issues/115
18:08:26bougymani'm very new to nim (like this-morning) so don't know how to test that ssl is working.
18:08:49bougymanis there a nim repl?
18:09:55dom96bougyman: Can you try Nim 0.10.3?
18:11:10thotypouswhere is 0.10.3? "devel" branch?
18:11:30bougymandom96: is that a release?
18:11:39dom96devel branch
18:11:44*vendethiel quit (Ping timeout: 246 seconds)
18:11:46dom96bougyman: no
18:12:13BlaXpirit_bougyman, i don't find repl useful. it is much better to just have a window to write code in and press run
18:12:29BlaXpirit_(aporia does that well)
18:12:41BlaXpirit_but, there is this https://github.com/wheineman/nrpl
18:13:02bougymanBlaXpirit_: for me everything starts on the repl.
18:13:08bougymanblame LISP, it was my first language.
18:13:16BlaXpirit_your loss
18:14:03bougymana tightly-intergrated repl-editor-debugger loop doesn't feel like a loss, to me. everyone has the flow which suits them ebst.
18:14:51thotypousbougyman: there is "nim i", but it is currently very limited, most things don't run
18:15:17BlaXpirit_disregard it
18:28:39*HakanD___ quit (Quit: Be back later ...)
18:29:14*HakanD___ joined #nim
18:29:25*vendethiel joined #nim
18:32:08*fichtl joined #nim
18:33:13*fichtl quit (Client Quit)
18:33:19*smelod quit (Quit: Leaving)
18:33:22*HakanD___ quit (Ping timeout: 250 seconds)
18:44:22*filcuc joined #nim
18:48:43*HakanD___ joined #nim
18:51:26*Pisuke joined #nim
18:53:09*filcuc quit (Ping timeout: 276 seconds)
18:55:48*filcuc joined #nim
19:02:06*ingsoc quit (Quit: Leaving.)
19:02:37*banister joined #nim
19:17:58*gsingh93 quit (Ping timeout: 255 seconds)
19:18:25*smodo joined #nim
19:23:51*HakanD___ quit (Quit: Be back later ...)
19:24:51*OnO quit (Quit: Textual IRC Client: www.textualapp.com)
19:29:15*ehaliewicz joined #nim
19:30:26*untitaker quit (Quit: ZNC - http://znc.in)
19:45:32*HakanD___ joined #nim
19:46:12*HakanD___ quit (Client Quit)
19:54:28*gokr joined #nim
19:55:27*TEttinger quit (Ping timeout: 250 seconds)
19:57:51*filwit joined #nim
20:08:34*renesac quit (Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/)
20:10:40*HakanD___ joined #nim
20:14:17*smodo quit (Ping timeout: 256 seconds)
20:14:17*Ettore joined #nim
20:23:45*Matthias247 joined #nim
20:30:44*dhasenan joined #nim
20:38:13*filwit quit (Quit: Leaving)
20:43:41*justicefries joined #nim
20:46:10*justicefries quit (Client Quit)
20:58:54*BlaXpirit joined #nim
20:59:27*BlaXpirit_ quit (Quit: Quit Konversation)
21:01:15*Trustable quit (Remote host closed the connection)
21:03:33*BlaXpirit quit (Read error: Connection reset by peer)
21:03:46*BlaXpirit joined #nim
21:05:36*mpthrapp quit (Remote host closed the connection)
21:23:54*shodan45 joined #nim
21:40:13*justicefries joined #nim
21:43:35*ehaliewicz quit (Remote host closed the connection)
21:46:41*HakanD___ quit (Quit: Be back later ...)
22:06:34ldleworkCan anyone tell me about Nim's feasibility in replacing the usecase of Vala?
22:06:44ldleworkJust like, philosophically. I know not much has been done.
22:09:32federico2oh, vala
22:09:47ldleworkfederico2: where the main problem being solved is gobject interoperability
22:16:05federico2hm, it could be nice to have an introductory wiki page with a list of usage scenarios where Nim is a good fit and why (and where is not and why)
22:18:22*justicefries quit (Quit: My Mac has gone to sleep. ZZZzzz…)
22:21:36*dhasenan left #nim (#nim)
22:24:38Araqfederico2: write it ;-)
22:26:20*brson quit (Quit: leaving)
22:28:41federico2gladly - where?
22:28:59*wb quit (Ping timeout: 265 seconds)
22:29:40Araqgithub wiki?
22:30:01federico2I mean - at what location in the wiki?
22:30:56BlaXpiritnew page called "an introductory wiki page with a list of usage scenarios where Nim is a good fit and why (and where is not and why)"
22:33:45*BlaXpirit quit (Quit: Quit Konversation)
22:36:20*Matthias247 quit (Read error: Connection reset by peer)
22:42:11*filcuc quit (Quit: Konversation terminated!)
22:49:07*justicefries joined #nim
22:51:27*elbow_jason joined #nim
22:52:38*thotypous quit (Quit: WeeChat 1.1.1)
22:57:22*elbow_jason quit (Remote host closed the connection)
22:57:35*elbow_jason joined #nim
23:09:25*bjz quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
23:16:20*justicefries quit (Quit: My Mac has gone to sleep. ZZZzzz…)
23:27:18*a5i joined #nim
23:34:24*Ettore quit (Quit: Leaving.)
23:34:42*saml_ joined #nim
23:43:09reactormonkso where do I need to put nimsuggest such that it finds e.g. strutils?
23:44:46Araqnimsuggest is simply like 'nim' itself
23:44:59Araqdunno what's so hard to understand about it
23:45:16Araqwhere do you put 'nim' so that it finds e..g strutils?
23:48:43reactormonkhttp://pastie.org/10106500
23:49:59*TEttinger joined #nim
23:51:14Araqreactormonk: cp compiler/nimsuggest/nimsuggest bin/nimsuggest
23:55:32onionhammeraraq any updates to nimsuggest lately?
23:56:10Araqonionhammer: yes but nothing about the bugs you reported, well in fact, I couldn't reproduce these
23:56:52onionhammeraraq hm ok
23:56:52a5iAloha
23:59:29reactormonka5i, neat, works.
23:59:29onionhammeraraq what about when u ran the python app
23:59:41reactormonkehh @ Araq, IRC laggy.