<< 30-04-2015 >>

00:00:18*Jesin quit (Quit: Leaving)
00:00:33*vendethiel quit (Ping timeout: 276 seconds)
00:01:00*Jesin joined #nim
00:04:49def-Haven't noticed anything, currently updates fine for me
00:11:27boydgreenfielddef-: Hmm lovely. I get it on both my machine and a remote Ubuntu server (on CircleCI). Here’s the request object that causes the error, even though wget/browser works fine (via a redirect, so potentially an issue there): (version: 1.1, status: 404 Not Found, headers: {Date: Thu, 30 Apr 2015 00:09:56 GMT, Strict-Transport-Security: max-age=31536000, Accept-Ranges: bytes, X-XSS-Protection: 1; mode=block, X-Frame-Options:
00:11:28boydgreenfielddeny, Content-Length: 9, Vary: Authorization,Accept-Encoding, X-Cache-Hits: 1, X-Served-By: cache-sea1926-SEA, Expires: Thu, 30 Apr 2015 00:14:56 GMT, Content-Security-Policy: default-src 'none', Connection: keep-alive, Access-Control-Allow-Origin: https://render.githubusercontent.com, X-Content-Type-Options: nosniff, Via: 1.1 varnish, Source-Age: 34, X-Cache: HIT}, body: Not Found)
00:21:48*shodan45 joined #nim
00:35:40filwithow come len() now checks for nil but add() does not?
00:41:36filwitanyways, g2g
00:41:38*filwit quit (Quit: Leaving)
00:42:33dom96boydgreenfield: odd
00:42:53dom96It works fine for me on Windows.
00:43:00dom96Have you updated Nimble recently?
00:45:36boydgreenfielddom96: Locally I’m on the v0.6.0 tag, but on CircleCI it’s going from master (same problem in both places, on Nim v0.10.2 on both)
00:46:05dom96boydgreenfield: can you test it with 0.10.3?
00:52:06boydgreenfielddom96: I can a bit later; lots of other tests were falling down for me on the v0.10.3 switch, so I held off earlier today on a full code port (waiting on the next stable, since I actually have some code in prod here)
00:53:00dom96sure, let me know how it goes when you do.
00:53:02dom96Good night.
00:58:58onionhammerVarriount did you see this? https://code.visualstudio.com/docs
00:59:14onionhammerneeds a nim plugin... once they open it up for plugins :)
01:06:44*darkf joined #nim
01:26:45boydgreenfielddom96: Appears to work on this remote machine, of course now some of my damned tests fail
01:27:01boydgreenfield(not your fault of course :) )
01:27:51boydgreenfield(under v0.10.3 / v0.11)
01:28:34*boydgreenfield quit (Quit: boydgreenfield)
01:34:34*Jehan_ quit (Quit: Leaving)
01:42:52Varriountonionhammer: Is there any indication that it will support plugins? If so, what language(s) can be used?
02:01:22onionhammerVarriount im guessing html/js to customize
02:01:32onionhammerbut yeah it says on that page i linked that they will allow 3rd party plugins
02:02:26onionhammer"Visual Studio Code will include a public extensibility model that lets developers build and use plug-ins, and richly customize their edit-build-debug experience."
02:08:14VarriountI'd prefer python, since that would make porting code just a bit easier.
02:08:25Varriount(hopefully)
02:08:38VarriountThen again, if we could write the plugin in Nim...
02:08:57*elbow_jason joined #nim
02:09:06elbow_jasonhey all
02:09:10VarriountHi
02:09:14elbow_jasonis there a way to define a pragma?
02:09:15onionhammerVarriount afaik it's similar to atom
02:09:29elbow_jasoni'm sitting at a meetup and we're talking about nim
02:09:45Varriountelbow_jason: Yes, using the 'pragma' pragma
02:10:03elbow_jasonthat's a bit hilarious
02:10:10elbow_jasonVarriount: ty
02:10:14Varriounthttp://nim-lang.org/manual.html#pragma-pragma
02:10:51Varriountelbow_jason: Glad to see you didn't get confused. I hoped the parenthesis clarified the name.
02:11:26elbow_jasonhehe.. we're going throught theindex.html at the moment. :)
02:35:09*jholland quit (Quit: Connection closed for inactivity)
02:36:12*BitPuffin|osx quit (Ping timeout: 252 seconds)
02:48:37*ir2ivps10 quit (Remote host closed the connection)
02:48:45*ir2ivps10 joined #nim
02:58:19*vendethiel joined #nim
03:08:41*saml_ joined #nim
03:09:34*elbow_jason quit (Ping timeout: 255 seconds)
03:13:43*johnsoft quit (Read error: No route to host)
03:13:53*johnsoft joined #nim
03:14:54*brson quit (Quit: leaving)
03:23:31*renesac quit (Ping timeout: 255 seconds)
03:37:39*renesac joined #nim
03:45:46*aboisvert joined #nim
03:47:56*aboisvert quit (Client Quit)
03:54:55*endragor joined #nim
04:03:33*vendethiel quit (Ping timeout: 250 seconds)
04:27:25*TEttinger quit (Ping timeout: 264 seconds)
04:31:16*johnsoft quit (Ping timeout: 244 seconds)
04:31:34*johnsoft joined #nim
04:45:47*BlaXpirit joined #nim
05:08:06*saml_ quit (Quit: Leaving)
05:22:32*HakanD joined #nim
05:23:11*yglukhov joined #nim
05:24:30*banister quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
05:27:47*yglukhov quit (Ping timeout: 265 seconds)
05:31:23*phira joined #nim
05:33:53*TEttinger joined #nim
05:34:02*HakanD quit (Quit: Be back later ...)
05:34:24*TEttinger quit (Client Quit)
05:35:57*Varriount_ joined #nim
05:39:01*Varriount quit (Ping timeout: 256 seconds)
05:47:56*banister joined #nim
06:10:21*HakanD joined #nim
06:18:05*MyMind quit (Read error: Connection reset by peer)
06:18:59*MyMind joined #nim
06:21:04*silven joined #nim
06:22:48*OnO joined #nim
06:32:10*Varriount_ quit (Read error: Connection reset by peer)
06:32:38*Varriount_ joined #nim
06:33:46*Demon_Fox joined #nim
06:48:47*yglukhov joined #nim
07:04:50*endragor_ joined #nim
07:06:46*pafmaf joined #nim
07:08:31*endragor quit (Ping timeout: 255 seconds)
07:09:26*pafmaf quit (Client Quit)
07:12:16*Araq quit (Ping timeout: 240 seconds)
07:13:46*Araq joined #nim
07:17:56*banister quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
07:40:47gokrMorning fellas
07:44:42*banister joined #nim
07:59:27*banister quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
08:01:06*bluenote joined #nim
08:02:11*coffeepot joined #nim
08:04:50*TEttinger joined #nim
08:06:40*HakanD_ joined #nim
08:06:40*HakanD quit (Read error: Connection reset by peer)
08:12:00*BlaXpirit quit (Quit: Quit Konversation)
08:12:38*Trustable joined #nim
08:17:56*endragor_ quit (Remote host closed the connection)
08:18:45*endragor joined #nim
08:26:36Araqgokr: the release is here: http://nim-lang.org/0.11.0/
08:27:41Araqfeedback appreciated before I switch over to this version of the website
08:27:50HakanD_\o/
08:29:19gokrI can test it
08:29:39gokrAh, you mean the release note etc
08:32:05*mal`` quit (Ping timeout: 276 seconds)
08:34:43*MyMind quit (Read error: Connection reset by peer)
08:35:46*MyMind joined #nim
08:36:30def-Araq: some links in lib.html don't work, for example sdl
08:36:31*Ven joined #nim
08:37:51*Ven quit (Client Quit)
08:39:44Araqah good catch, that's a nimble package now
08:45:09HakanD_http://nim-lang.org/0.11.0/rationals.html, http://nim-lang.org/0.11.0/dialogs.html, http://nim-lang.org/0.11.0/web.html
08:45:13HakanD_all from http://nim-lang.org/0.11.0/lib.html
08:45:14HakanD_not working
08:47:42*mal`` joined #nim
08:48:31HakanD_http://www.deadlinkchecker.com/
08:50:17*Ven joined #nim
08:50:17fowlAraq, macros.getType isnt mentioned
08:50:33Araqfowl: that's a minor feature *cough*
08:50:38Araqgood point
08:53:22fowlTypeless parameters are now only allowed in templates and macros. The old way turned out to be too error-prone. - does "any" still work?
08:55:10Araqwell actually, they continue to work
08:55:19Araqand produce only a deprecation warning
08:55:28def-Araq: nimsuggest in news doesn't link anywhere
08:55:42Araqdef-: yup, I'm writing its docs as we speak
08:55:47def-great
08:59:15fowlwhere can i set cc=vcc
08:59:40def-$nim/config/nim.cfg or any local config
08:59:45fowlin ~/ somewhere hopefully?
09:00:32fowlit gets overridden
09:04:05gokrMy main feedback on the release note is that... Removal of "Typeless parameters" should perhaps be explained a bit more.
09:09:31*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
09:15:15*ingsoc joined #nim
09:17:41def-Araq: I think we should also have a nim-0.11.0.tar.xz. 4 MB vs 28 MB for the zip may be quite a difference for some people
09:18:01AraqI don't know where you get that 4 MB number from
09:18:14Araqthe tar.gz was *24* MB
09:18:20def-I extracted the zip and made a tar.xz
09:18:24def-*xz*, not *gz*
09:18:38Araqaha
09:21:03Araqwell I've automated the release building properly and everything that requires me to switch OSes is bad
09:22:15def-Araq: 7zip can do tar.xz i think (with wrong executable bits of course)
09:22:16Araqso ... I'm sure I can produce xz, but it will have the executable bits set which sucks
09:31:43*Sembei joined #nim
09:33:26*phira quit (Quit: ZNC - http://znc.sourceforge.net)
09:33:30Araqdef-: I can produce a .7z which is 2.67 MB
09:34:22Araq142MB compressed down to 2.67. Not bad.
09:34:38def-but 7z is not as common as tar.xz on *nix
09:35:30Araqit's not common on windows either. but we need to drag these OSes into the 20th century at least
09:36:52*milosn quit (Quit: leaving)
09:37:02*HakanD__ joined #nim
09:37:06gokrEh, xz is 7z, but with support for Unix metadata.
09:37:19Araqah interesting lol
09:37:47Araqand we lack that precious metadata, so 7z is fine
09:38:08def-the 7z tool is not fine at all on non-Windows platforms
09:39:29def-I don't have 7z or zip installed on any of my servers. tar.xz works on each of them
09:40:57def-I can build the tar.xz for you, but I don't see a way to do it properly on Windows
09:41:03*HakanD_ quit (Ping timeout: 265 seconds)
09:41:44Araqdoesn't unzip or whatever you use on unix work with 7z?
09:43:00def-you use tar on unix and it works with tar.{bz2,xz,gz} files, not with 7z
09:50:46*milosn joined #nim
09:51:23*milosn quit (Client Quit)
10:01:25*OnwardEuler joined #nim
10:09:14coffeepotcongratulations on the new release :)
10:09:35OnwardEulersweet, there's a new release?
10:10:48OnwardEulerwhat's new in 0.11=
10:10:49OnwardEuler?=
10:10:57coffeepothttp://nim-lang.org/0.11.0/news.html#Z2015-04-30-version-0-11-0-released
10:11:09def-It's not released yet, that's the preparation
10:11:18OnwardEulerthank you, sir!
10:11:53coffeepotyeah probably best to reiterate what def said, not quite a new release yet!
10:12:21*milosn joined #nim
10:19:56*Ven joined #nim
10:25:55coffeepot"const foo = {"ah": "finally", "this": "is", "possible.": "nice!"}.toTable()" noice
10:30:35*Kingsquee quit (Quit: Konversation terminated!)
10:31:51dom96I agree with def-, let's get a tar.xz
10:32:18dom96I also think the release notes need a bit more text.
10:32:35gokrI spoke to Araq and he will try building the tar ball with "tar" instead :)
10:32:41fowlAraq, interface is not quite ready, there is still more things i want to do to make it more safe
10:32:46gokrSince its actually included in the git installed.
10:33:22gokrAlso... is xz much better than bz2?
10:33:23fowlright now you would probably blow the world if you used a varargs function with it for ex
10:33:31def-gokr: yes, decompression is sooo much faster
10:33:55gokrAnd... xz is as universally available on Unices as bz2?
10:33:58fowlgn all
10:34:01gokrgnite
10:34:44dom96Araq: You can build a tar.xz using 7zip on Windows.
10:34:44def-gokr: not if you have a really old distro, but in the last years many huge projects are switching to xz
10:34:53def-dom96: that sets +x on every file
10:35:05def-dom96: I'd like +x on the shell scripts, but seems like that won't work on Windows
10:35:14dom96bah
10:35:36gokrdom96: He will try using tar instead, but he is away for lunch
10:36:11dom96Alright.
10:36:53dom96I would like to write a bit more in the intro to the release notes, or do you guys think that's not necessary?
10:37:08gokrI also thought that.
10:37:39def-gokr: the 2.6 MB tar.xz extracts into 153 MB in 0.9 seconds for me. I can only get .tar.bz2 down to 18 MB and that needs 2.3 seconds to decompress
10:37:39gokrLike say "This means that this version of the *language* is quite close to 1.0, although the standard library needs more work." Although I am not sure that's a lie :)
10:38:12gokrdef-: Ok, just noted however that "xz" seems not to be included in the git install on Windows.
10:38:33gokrSo "-cJf" didn't fly.
10:47:36gokrAraq: I just downloaded http://tukaani.org/xz/xz-5.2.1-windows.zip and threw in the binaries in the bin_x86-64 directory into my git\bin directory. Then you can do "tar cJf blabla.tar.xz blabla"
10:50:04*vikaton joined #nim
10:51:53*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
10:53:12dom96This is what I have so far: https://gist.github.com/dom96/7ed84d5d56ba4d410db0
11:02:14coffeepotdid someone say that sdl is now a nimble package and not in the stl?
11:02:21coffeepotstdlib
11:02:45*iamd3vil joined #nim
11:03:36*iamd3vil quit (Remote host closed the connection)
11:03:46*iamd3vil joined #nim
11:03:47*iamd3vil quit (Remote host closed the connection)
11:06:07flyxhaving written code in a dozen languages and adhering to quite some styleguides, I notice that my code is rather inconsistent with identifier name conventions. does anyone else have this problem?
11:06:10dom96If it is then this shouldn't exist: http://nim-lang.org/0.11.0/graphics.html
11:07:35coffeepotit is nice to have some form of graphics in the stdlib
11:08:02coffeepotalthough iirc you do need to find/combile sdl.dll
11:08:06coffeepotcompile
11:10:55coffeepoti'm hacking out a physics library in nim atm, it would be amazing to have something like that in the stdlib (dunno if this would be a popular idea) but I feel if that's the case then it should probably be a higher level module for a bullet wrapper or something (though, again bullet would need to be compiled to the dll to be used iirc)
11:11:45coffeepotahem, sorry, rambling :)
11:16:27gokrPersonally I can't see physics belonging to a stdlib.
11:16:55gokrWhat's the argument for being "in the stdlib"?
11:19:46coffeepotthat's fair enough gokr. It'd be better as a nimble package. Good question though, what is the requirement for being the stdlib?
11:19:48OnwardEulerI'm working on a little game engine in nim
11:19:58OnwardEulerusing the sdl2 packages
11:20:29OnwardEulerI find that graphical work is fairly alright just with that package
11:20:44Araqflyx: yeah. that's the reason why real professionals don't give a fuck about casing. ;-)
11:22:01flyxAraq: I'm just thinking about defining some style *I* want to adhere to when writing Nim code
11:22:21Araqflyx: we have a style guide in the wiki that we stick to
11:22:30flyxah, nice
11:23:02dom96Araq: shouldn't the graphics module be deleted?
11:23:14Araqdom96: it should be a nimble package, but isn't
11:23:32Araqsame for dialogs
11:23:47dom96Well, is the sdl module gone?
11:23:48Araqbut dialogs is an interesting case. it depends on gtk2 but not on windows
11:24:04coffeepotis the stdlib just stuff that doesn't have any dependancies?
11:24:19Araqdom96: dunno if nimble can model conditional dependencies
11:24:29dom96Araq: it can't
11:24:44Araqdom96: SDL is still in the stdlib but most people use the Nimble package now I think
11:24:53dom96right.
11:24:57Araqit's a wrapper for SDL-1.2, most now use SDL-2
11:25:05dom96well, I guess for the next release we will sort out the standard lib
11:25:12Araqyup
11:25:19dom96do you like my intro?
11:25:21coffeepotsdl seems easier for basic graphics, doesn't sdl2 rely on opengl?
11:25:31Araqdom96: I'm not sure it's correct :-)
11:25:42*HakanD__ quit (Quit: Be back later ...)
11:26:06Araqcoffeepot: IMHO SDL-2 disqualifies as a library since it requires a custom main
11:26:19Araqwhich is mind-bogglingly stupid
11:26:50dom96Araq: What's not correct about it?
11:27:15coffeepotyes that's an interesting requirement for a library
11:27:19Araq"The *language* itself is very close to 1.0, the primary area that requires more work is the standard library."
11:29:25dom96ok, well, i'll commit it anyway and you can modify it :P
11:29:33Araqok
11:30:33Araqfowl: 'interface' wasn't promised for 0.11.0 at all.
11:31:19dom96done
11:33:02*JinShil joined #nim
11:35:19gokrNo idea if there is a "policy" regarding stdlib, but two things that comes to my mind in that area is that one would expect the stdlib to be maintained by the project/community - and thus it needs to be reasonably small and above all perhaps, reasonably general purpose (since Nim is a general purp lang).
11:35:53Araqgokr: the policy is mostly about who maintains it
11:35:58gokrWell, that was the 1st thing, the 2nd thing I was thinking of is the fact that when code is "community maintained" it may have a tendency to rot.
11:36:25gokrI say "may" because perhaps different projects work differently.
11:36:27Araqtendency to rot also exists with modules that are in the stdlib but we don't care about
11:36:41Araqor use for that matter.
11:36:43gokrRight.
11:37:13gokrI do know from Squeak/Pharo that... when code enters the "image" (=stdlib) people suddenly are afraid of improving on it.
11:38:23gokrSometimes for a good reason - I mean - being conservative and backwards compatible etc. But often just because ... "shared responsibility is no responsibility".
11:39:09def-Araq: are you interested in binary builds for other platforms for the release?
11:40:33Araqyes, but I don't want another "this version has binaries, and ... this doesn't cause the guy who built it wasn't available"
11:41:21dom96We need a build farm which can build these binaries/installers.
11:41:39Araqdom96: exactly. but we haven't.
11:43:18def-can't use the buildbot.nim-lang.org thing for that?
11:43:55Araqin theory we could do that. in practice Varriount_ has no time.
11:44:19*milosn quit (Quit: leaving)
11:46:21*HakanD__ joined #nim
11:46:29*TEttinger quit (Ping timeout: 248 seconds)
11:47:06def-Araq: git archive can create tars and apparently preserves executable bit. not sure if that's an option in your building process
11:48:03Araqbut what is there to "preserve"? there is no exec bit on windows.
11:48:25def-but in the Nim git repo the executable bit of shell scripts is there
11:48:50Araqhrm
11:48:53Araqwill try
11:49:21*HakanD___ joined #nim
11:53:01*HakanD__ quit (Ping timeout: 256 seconds)
12:05:15*BlaXpirit joined #nim
12:07:21*BitPuffin|osx joined #nim
12:09:28*BlaXpirit-UA joined #nim
12:12:37*BlaXpirit quit (Ping timeout: 248 seconds)
12:14:39bluenotehm, is the following behavior intended: (?)
12:14:45bluenoteI have a bin and a src folder and try to compile "nim c -r -o:bin/main src/main.nim"
12:15:02bluenotehowever, the compiler tries to output the file to "src/bin/main"
12:15:16bluenoteI can work around that by "nim c -r -o:../bin/main src/main.nim"
12:15:24bluenotebut then "-r" does no longer work, i.e., nim fails to execute its own output resulting in "sh: 1: ./../bin/main: not found"
12:15:57Araqno, it's a known bug, but fixing it will break somebody's build I think :-/
12:16:27Araq-o wasn't really designed for Nim, it's for "nim doc2" ...
12:16:29bluenoteok, thanks!
12:16:52Araqand then people complained it doesn't work ...
12:20:37bluenotewell, separating the binary output from the source is probably something many people will try
12:23:35bluenotewhat about keeping the behavior that we need -o:../bin/blah and simply adapting the path where "-r" looks for the output?
12:23:55bluenotethis should not break anything, since -r is broken anyway with -o
12:23:56bluenote?
12:24:27Araqno, let's just fix it instead
12:25:17Araqwe need to rework path handling in the compiler anyway ... this will break stuff. again.
12:27:53*Ven joined #nim
12:33:56*saml_ joined #nim
12:41:03flyxwhy isn't \n allowed in a character literal?
12:41:17def-flyx: it's 2 characters on windows
12:41:19BlaXpirit-UA\l is \n
12:41:26flyxah
12:41:27flyxI see
12:41:33BlaXpirit-UA\n can be 2 chars
12:46:17*BitPuffin|osx quit (Ping timeout: 256 seconds)
12:47:13*coffeepot quit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
12:47:28*coffeepot joined #nim
12:55:34*mpthrapp joined #nim
13:09:56*HakanD___ quit (Read error: Connection reset by peer)
13:10:23*HakanD___ joined #nim
13:21:46*saml_ quit (Read error: Connection reset by peer)
13:24:06*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
13:26:15bluenoteI'm not sure if https://github.com/Araq/Nim/issues/2355 is really fixed
13:26:28bluenoteshouldn't this fail: https://gist.github.com/bluenote10/d83eb35a34de309af177
13:27:29Araqbluenote: doesn't produce a warning?
13:27:57Araqyes it does.
13:28:08Araq"Warning: Cannot prove that 't' is initialized."
13:28:08bluenoteah, got it "This will become a compile time error in the future."
13:28:35bluenoteI was assuming the compiler already refuses to compile this...
13:29:40*banister joined #nim
13:33:06bluenote...because the compiler already produces an error when I initialize the field as nil _explicitly_.
13:42:44*ingsoc quit (Ping timeout: 265 seconds)
13:44:28Araqbluenote: well not directly related to that but ... I'd really prefer people would submit real tests instead of these trimmed toy examples that are filling up our tests directory
13:46:10Araqtrimmed down examples help when it fails at runtime, but not so much for compiletime bugs
13:47:12Araqand the danger is that there is an overfitting of the compiler to these toy examples
13:48:11bluenoteyeah, especially for such cases where the compiler has to infer complex information/relations...
13:49:42bluenotefor instance I just had this case: type A = seq[blah]; type B = seq[otherblah] not nil
13:50:28bluenotein my code I had an A which was not nil at runtime, and I was mapping over it so that the types changed from "blah" to "otherblah"
13:50:48bluenotethe result obviously must be "not nil" since the original sequence was not nil
13:51:36bluenotebut interestingly the compiler will give an error since it cannot prove "not nil" in this case
13:53:19Araqwell it helps to think of it as if Nim did like the others do. So 'seq' is Optional[T] and 'seq not nil' is 'T' and then instead of pattern matching you can do 'if not x.isNil:'
13:53:29*Demos joined #nim
13:53:42Araqthe analyis is not much smarter than that
13:54:13Araqthis explains for instance why 'if x.isNil: return' doesn't help
13:54:28Araqbut 'if not x.isNil: ... body here ... ' does
13:54:53*BitPuffin|osx joined #nim
13:55:09*Ven joined #nim
13:55:10bluenoteyes, this makes sense
13:56:41Araqthat said, that "flow typing" that Nim uses is now used also to enforce locking etc., so it's quite consistently applied and a very powerful idea
13:58:13Araqwell ... not that "powerful" but I love the complexity vs expressivity tradeoff of it
13:58:16*dom96_ joined #nim
13:59:48*Ven quit (Read error: No route to host)
14:00:11*ingsoc joined #nim
14:00:33bluenoteimho having the compiler to force something like not nil is definitely "powerful"
14:06:26*Ven joined #nim
14:10:00coffeepotis there currently a way to query metrics about memory operations, current memory overhead or other statistics from the GC? Or can I get this info better from a profiling tool (if so any recommendations)?
14:10:36def-coffeepot: GC_getStatistics()
14:10:47coffeepotyay! Cheers def- :)
14:12:34coffeepotthat is sweet
14:16:37Araqcoffeepot: before you parse that info ... make a PR to expose the stuff in a typed manner
14:19:24*saml quit (Quit: Leaving)
14:20:22*jholland joined #nim
14:23:43*darkf quit (Quit: Leaving)
14:23:47coffeepotok, sure :) I guess I'll have to actually create a github account then ;)
14:27:27*saml joined #nim
14:38:13*dom96_ quit (Ping timeout: 246 seconds)
14:41:58*milosn joined #nim
14:47:33*zama quit (Ping timeout: 256 seconds)
14:54:05*zama joined #nim
15:02:53*dom96 quit (Changing host)
15:02:53*dom96 joined #nim
15:06:53*Trustable quit (Remote host closed the connection)
15:07:41coffeepotSo this is it, 0.11 is officially released?
15:07:45*Trustable joined #nim
15:10:12dom96yep
15:10:24bluenotewhat is the current state of the future module btw?
15:10:41bluenoteI cannot get the passTwoAndTwo example to work
15:11:29bluenoteI mean withour warnings like: Warning: '(x; y): auto' has no type. Typeless parameters are deprecated; only allowed for 'template' [TypelessParam]
15:12:32dom96My plan is to have that stuff in the system module
15:12:48dom96not sure if Araq will agree
15:13:43bluenote+100 for making this part of system :)
15:14:43bluenotebut will it be possible to use anonymous functions without type annotations considering typeless parameters are deprecated?
15:16:10Araqyeah, the macro needs to expand to proc (x, y: auto): auto = ...
15:16:17Araqthe feature is not gone
15:16:21Araqbbl
15:17:37*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
15:18:18bluenoteyes, and it seems to work, I was just worried about the warnings
15:18:31coffeepotI love the way everything you need to use nim is included in a single installer for windows, it's just great. Minor note for dom96 though - and this might have just been my system - but compiling failed and causes Aporia to quit because edit/preferences/tools had this in the nim exe edit box "$findExe(nimrod) c --listFullPaths $#" when it should ha
15:18:31coffeepotve been "$findExe(nim) c --listFullPaths $#"
15:19:13dom96argh, damn. That's a bad issue.
15:21:47coffeepotjust to clarify, nim was installed correctly and everything works, it was just a setting in Aporia that needed changing so it could find the exe
15:22:37coffeepotI've had various versions of nim installed though, could it be an old register settings? I usually use sublime as my editor so I haven't used Aporia in a while
15:23:07dom96Have you used Aporia before?
15:23:41coffeepotyes but ages ago
15:23:46*Ven joined #nim
15:23:50dom96ahh, that's good.
15:23:52dom96https://github.com/nim-lang/Aporia/blob/master/cfg.nim#L40
15:24:00dom96Seems it has been fixed, whew.
15:24:18coffeepot:) so it's probably just an old setting for me then :D
15:24:19*vendethiel joined #nim
15:25:44dom96yep
15:25:57dom96Aporia shouldn't crash though heh
15:26:45coffeepotanother old setting that's probably just me too is that the shortcut on my start menu points to C:\Nim\dist\aporia\bin whereas the exe is actually located in C:\Nim\dist\aporia-0.3.0\bin
15:26:58coffeepotsorry hopefully not causing undue stress here!
15:27:21coffeepotmy system isn't a clean install because the uninstaller didn't run
15:28:48dom96we can always fix the installer if bugs are found
15:28:52*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
15:28:56coffeepotfwiw the shortcut on my start menu is dated march 17th this year so it's probably just old data again ;)
15:29:05dom96indeed
15:31:25coffeepotsorry dom :) congratulations on the release again, things are really getting exciting for nim :D
15:31:40dom96hehe, no worries. Thank you for testing it.
15:32:26coffeepotnp :D
15:41:50*Matthias247 joined #nim
15:43:58*Ven joined #nim
15:46:01*OnwardEuler quit (Quit: Leaving)
15:49:28*Arrrrrr joined #nim
15:49:42ArrrrrrHello. Congratulations nim community for this release.
15:57:53*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
16:01:27*yglukhov quit (Quit: Be back later ...)
16:06:15*gsingh93 joined #nim
16:10:08*vendethiel quit (Ping timeout: 265 seconds)
16:10:58*bluenote quit (Ping timeout: 246 seconds)
16:13:18*vendethiel joined #nim
16:14:14TrustableI get "Error: unhandled exception: invalid format string [ValueError]" when Nim tries to compile cairo for a gtk2 programm
16:14:40TrustableHow can I get more information about the error?
16:16:17dom96./koch temp c cairo.nim
16:19:00*MightyJoe is now known as cyraxjoe
16:20:39Trustabledome96, thx, problem is the kown one: could not import: CreateSymbolicLinkW
16:21:32*coffeepot quit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
16:22:46Trustableoh, I think I can fix it with deadCodeElim:on, but this does not help
16:33:39BlaXpirit-UAnoice
16:40:24*yglukhov joined #nim
16:44:47*BlaXpirit-UA quit (Quit: Quit Konversation)
16:46:44*BlaXpirit joined #nim
16:48:14ldleworkcongrats on the release, peoples of Nim
16:50:45*pidg joined #nim
16:54:17*hguux____ quit (Quit: Connection closed for inactivity)
16:56:00*OnO quit (Quit: My iMac has gone to sleep. ZZZzzz…)
16:58:27*vendethiel quit (Ping timeout: 256 seconds)
17:04:40BlaXpiritare the commits to master just gonna continue or maybe it's time to do something about this
17:05:14BlaXpiritand by commits I mean accidental commits
17:09:13def-BlaXpirit: sure, how to fix it?
17:09:40BlaXpiritnot have the stable branch named "master"
17:10:03def-I don't think that's the source of the problem
17:10:08BlaXpiritof course it is
17:10:28BlaXpiriteveryone knows master is what you base your contributions on
17:10:37def-people click through the documentation on the source code link and that leads them to this branch, so they fix typos directly there and make the PR
17:10:58BlaXpirithm maybe
17:11:18def-but i still agree that master should be renamed to stable/release and devel to master
17:11:43BlaXpiritnot even necessary to rename devel to master
17:11:57ldleworkdo you really need a branch for stable/release?
17:12:04ldleworkjust tag releases.
17:12:21ldleworkmaster = development that passes tests
17:12:31ldleworkbranches = shit that may or may not work
17:12:37BlaXpiritsomething is definitely flawed there
17:12:38def-maybe there will be bugfix releases, so a branch may make sense
17:12:52BlaXpiritthe branch is supposed to be 0.11 then
17:13:16ldleworkdef-: in that case, agreed
17:13:25*OnO joined #nim
17:13:35*vendethiel joined #nim
17:13:36*Jesin quit (Quit: Leaving)
17:14:03ldleworkBut only commits that pass tests/review should be allowed to be merged, by way of feature-branch-pr
17:14:06ldleworkto master
17:14:16ldleworkyou should always be able to compile master, and get something that works
17:14:21ldleworksomething that you pass to nightly build system
17:15:08ldleworkshit that doesn't work, lives in a feature branch that undergoes review and iteration until its ready, tracked by an on-going early-PR
17:15:15ldleworkthat's how we do it anyway
17:15:17BlaXpiritwait a second
17:15:25BlaXpiritwhy do docs even link to a branch in the first place
17:15:30BlaXpiritwhy the heck is it not a tag
17:15:32*OnO quit (Client Quit)
17:15:59*OnO joined #nim
17:16:00BlaXpiritthat's the main problem!
17:16:18def-well, that's easy to fix then
17:16:54BlaXpiritbut then "everyone knows master is what you base your contributions on" point still stands
17:17:18BlaXpiritbtw in case someone finds this in search, that^ is currently not true for Nim
17:17:37*brson joined #nim
17:17:37*brson quit (Client Quit)
17:19:37*[dee] joined #nim
17:19:59*endragor quit (Ping timeout: 256 seconds)
17:20:24*Jesin joined #nim
17:20:33*OnO quit (Ping timeout: 256 seconds)
17:29:56AraqBlaXpirit: I'm open for suggestions. the master/devel split certainly makes no sense anymore.
17:30:05BlaXpiritldlework said it
17:31:07BlaXpiritof course, there is that convenience that you can clone git repository master and expect latest version
17:31:24BlaXpiritnot sure what the alternative would be
17:32:05Araqwell I dunno. maybe what we have does make some sense, if only we used it properly
17:32:23Araqbugfixes always can break somebody's code
17:32:42Araqso unless it's a critical fix, it should live in devel
17:33:20BlaXpiritwhat's typically done is branches like "0.11"
17:34:59BlaXpiritthe current model is not so bad
17:35:14BlaXpiritbut what definitely should be done is removing links to master in docs
17:35:20ldleworkGenerally, when you clone from version control, you're intersted in the development of the thing.
17:35:27ldleworkIf you want to clone a release, you look to a tag.
17:35:47BlaXpiritif linked to a tag, it says "you must be on a branch to make changes to this file"
17:35:59BlaXpiritldlework, how do you get latest release?
17:36:24ldleworkBlaXpirit: if you really need something other than picking the tag you're interested in, we can maintain a 'latest' tag
17:36:41ldleworkAs part of the release process
17:37:18ldleworkBut this is only how to do it, if you don't want separate master/devel branches
17:37:22*Varriount__ joined #nim
17:37:31BlaXpiriti rely on master here https://github.com/docopt/docopt.nim/blob/9b8a4/circle.yml
17:37:50BlaXpiritbecause i dont see a different way to get latest release
17:38:02ldleworkotherwise, master = latest release, devel = test-passing release-pending work, branches = features and version tracking
17:38:21ldleworkfeatures get merged into devel, and when devel accumulates enough for a release, devel is merged into master and tagged
17:38:43BlaXpiritthat's just not gonna work
17:38:53ldleworkI mean that's the 'true' git standard
17:39:35BlaXpiritgood unless you consider that devel compiler is an important product on its own
17:39:43Araqwell that's what we do (?)
17:39:56ldleworkit has nothing to do with the devel version being something independent
17:40:01*thotypous quit (Ping timeout: 264 seconds)
17:40:04ldleworkits about accumulating release commits
17:40:21Araqmaster = latest release, devel = test-passing stuff, branches for important stuff
17:40:22ldleworkits a version control thing, not a nim product thing
17:40:30ldleworkAraq: right, I don't think anything needs to change
17:40:46ldleworkBut we should link to tags not branches
17:41:08Araqyou mean for the "view source" feature in the docs?
17:41:15BlaXpiritmainly
17:41:22BlaXpiritmaybe there is something else
17:41:22ldleworkI only suggested the other thing, because I thought I read you guys were trying to figure out a way to do it without separate branches.
17:41:30ldleworkI don't actually recommend doing a latst tag, and all that.
17:41:50BlaXpiriti just cringe when i see those commits to master, that's all :|
17:41:58ldleworkNo one should be comitting to master.
17:42:07BlaXpiritand yet it happens
17:42:09ldleworkMaster should only accumulate commits via FF merges of devel
17:42:12*pleiosaur joined #nim
17:42:14BlaXpiritand that's what i brought up
17:42:22ldleworkAh that's an operational problem then :D
17:42:43BlaXpiritthese are accidental
17:42:57ldleworkAnd devel should only accumulate commits via PR merges via github interface
17:43:08AraqBlaXpirit: yeah, I dunno. when reviewing PRs I pay no attention to the branch
17:43:30*Matthias247 quit (Read error: Connection reset by peer)
17:43:35ldleworkAraq: time to start! lol
17:43:36BlaXpiritdef- implied that almost all of such pull requests are the result of people being linked to master in docs
17:43:43ldleworkBlaXpirit: makes sense
17:44:00ldleworkits no big deal just have to make a community effort to pay more attention to that
17:44:12ldlework"Please resubmit this against devel for inclusion in $NEXT_SEM_VER"
17:44:21BlaXpiritwe get it
17:44:28BlaXpiritbut it's accidental -_-
17:44:46ldleworkSorry didn't mean to be a broken record
17:45:28Araqer ... the "view source" feature is fucked up?!
17:45:38*n_v joined #nim
17:45:42*Amrykid2 joined #nim
17:45:42BlaXpiritlike we said already, it should not link to master
17:45:43Araqthese lines do not match at all. I wonder what's wrong here
17:45:54Araqbut master == devel right now?
17:45:59*vinnie joined #nim
17:46:00BlaXpiritAraq, well because master was updated and docs are implying old master
17:46:08BlaXpiritdocs weren't updated!
17:46:08Araqhow so?
17:46:19AraqI did update the docs, wait a sec
17:46:23BlaXpirite.g. re.html doesn't have my changes
17:46:35Araqwell it's in 0.11.0/re.html now
17:46:36*cazov_ joined #nim
17:46:46Araqit's now versionized
17:46:53*mtj__ joined #nim
17:46:59*saml quit (*.net *.split)
17:46:59*Varriount_ quit (*.net *.split)
17:46:59*n0v quit (*.net *.split)
17:46:59*cazov quit (*.net *.split)
17:46:59*vince- quit (*.net *.split)
17:46:59*mtj_ quit (*.net *.split)
17:46:59*BitPuffin|osx quit (*.net *.split)
17:47:00*Amrykid quit (*.net *.split)
17:47:00*reloc0 quit (*.net *.split)
17:47:00*pleiosau1 quit (*.net *.split)
17:47:00*[dee] quit (*.net *.split)
17:47:00*no_name quit (*.net *.split)
17:47:00*ChrisMAN quit (*.net *.split)
17:47:00*federico3 quit (*.net *.split)
17:47:00*skroll1 quit (*.net *.split)
17:47:00*heinrich5991 quit (*.net *.split)
17:47:02Araqbut some links are wrong, pointing to the old docs
17:47:13Araqwhich I left on this server for the time being
17:47:19*n_v is now known as n0v
17:47:19BlaXpiritAraq, please change links https://github.com/Araq/Nim/blob/master/lib/impure/re.nim#L26 -> https://github.com/Araq/Nim/blob/v0.11.0/lib/impure/re.nim#L26
17:47:35BlaXpiritthat's the main point
17:47:50Araqno something else is going on here
17:48:13BlaXpiriti'm not saying there isn't
17:48:41Araqoh no. it's just the old browser refresh problem for me
17:48:53Araqthe lines do match
17:49:39*ChrisMAN joined #nim
17:49:40*federico3 joined #nim
17:49:40*skroll1 joined #nim
17:49:40*heinrich5991 joined #nim
17:49:45*HakanD___ quit (Quit: Be back later ...)
17:50:24*shodan45 quit (Remote host closed the connection)
17:50:27BlaXpiritold locations of docs should be updated
17:50:42*shodan45 joined #nim
17:51:09AraqBlaXpirit: iirc one problem was that github doesn't link properly to particular commits. 'master' worked fine.
17:51:19Araqmaybe tags do too
17:51:28Araqor maybe github fixed the problem in general
17:52:11BlaXpiritnever seen anything like this
17:52:17BlaXpiritany such problem*
17:52:30*reloc0 joined #nim
17:53:24*[dee] joined #nim
17:53:37*saml joined #nim
17:54:16*no_name joined #nim
17:54:30federico3ooh there was a release today
17:57:10ArrrrrrYep, upvote http://redd.it/34ep78
17:58:25BlaXpiritall my libraries work, and have 0 deprecation messages
17:58:34BlaXpiritthat's nice
18:04:48*iamd3vil joined #nim
18:04:57federico3https://news.ycombinator.com/item?id=9465517
18:05:21federico3there's quite some whining about the case-insensivitiy in variable names
18:06:27BlaXpirithaters gonna hate
18:07:05*thotypous joined #nim
18:07:22BlaXpiriti got over the syntax
18:07:41federico3some are asking to change it or make it optional (sounds impossible)
18:08:00federico3but maybe a nice explanation would do
18:08:05ArrrrrrIndeed. Change it because you gonna make it working with grep ..
18:08:20BlaXpiritnope nope nope
18:08:28BlaXpiritit was just changed recently -_-
18:10:42ldleworkIs IDETools working these days?
18:17:50Arrrrrrkoch boot -d:release --deadCodeElim:on #could not import: CreateSymbolicLinkW
18:17:59Arrrrrrdom96: you told me i could pass deadCodeElim to koch
18:18:14keypusher0.11 release also mentioned here on HN https://news.ycombinator.com/item?id=9465517
18:20:31Arrrrrrok, i compiled koch with the switch on
18:20:45iamd3vilWhat should I clone? the devel or master branch for 0.11 release
18:20:52keypusherone complaint that stuck out to me was about partial case insensitivity, is there really a good argument for supporting this? i see in the docs it references allowing programmers with different styles to work on codebases and display identifiers the way they like, but it still seems weird to me
18:21:13Arrrrrri'd clone devel if i were you.
18:21:23dom96the v0.11.0 tag
18:21:28def-iamd3vil: right now it shouldn't matter. master will not be updated until next release, devel gets all the development inbetween releases
18:21:28dom96(or master)
18:22:03ArrrrrrIs both weird and a good argument.
18:23:07Araqkeypusher: the alternative seems to be enforce some_ugly_identifiers for compatibility with Python for functions and SomeOtherThing for types. Or we enforce javaStyleIdentifiers instead. well guess what. you can support both styles at the same time, pissing everybody off. Seems to be a nice compromise.
18:23:52Araqas a result we don't have to tell Nimble packagers to write everythingThisWay or everything_this_way.
18:23:52keypusherfair enough
18:23:57def-Araq: at least inside of a project the compiler could give a warning if you use identifiers inconsistently
18:24:42ArrrrrrAnyway most here seems to stick with the camelCase style
18:25:30ldleworkI'm going to take that as a no
18:25:46ldleworkI wish we had adopted lower_case_style :(
18:25:50Araqdef-: that's *lots* of work for no good reason.
18:26:27def-grepping is a good reason for me
18:26:30Arrrrrrlower_case is so ugly
18:26:41keypusherit does seem like it encourages inconsistent styles. i think personally i would prefer an opinionated stance on "The One Right Way" but I can understand not wanting to make that decision for people
18:26:44ldleworkIts the most vistually tokenizable
18:26:45Araqwe have better things to do than dreaming up ways of how to boss around our users.
18:27:02dom96We do have a stance: camelCase
18:27:21Araqdef-: so use nimgrep instead. that produces more readable output anyway.
18:27:34dom96if you're calling wrappers then using the wrapper's style is ok.
18:27:43ldleworkdef-: how often are you interested in a token in your app code and in the underlying library code at the same time?
18:27:52ldleworkYou can say a lot, but in my experience its usually one or the other.
18:28:01federico3indeed
18:28:04ldleworkNow having to remember what style the underlying library used, is annoying..
18:28:13def-Araq: I mean searching in general. most editors don't have a nim-aware search
18:28:38Araqdef-: most of the time the fact we avoid underscores is sufficient for that
18:28:58Araqtext based searches are never accurate for a programming language anyway
18:29:16Araqyou can always think of cases where grepping can fool you
18:30:16federico3indeed, ctags is your friend (or not)
18:30:29*boydgreenfield joined #nim
18:31:41keypusherit does add complexity to intellisense type code identifier resolution
18:31:54*OnO joined #nim
18:34:15ArrrrrrDoes it? How much complexity can it add?
18:34:41Araq~30 lines of code. perhaps.
18:35:05Arrrrrrhttp://nim-lang.org/manual.html#identifier-equality
18:39:41def-Anyway, I'm not saying that case sensitivity is better. both have problems
18:41:28keypusherjudging from the HN thread, most programmers seem to have a visceral reaction that case insensitivity is a bad idea
18:42:13BlaXpiritthe real problem is the existence of uglyCase
18:42:16federico3s/programmers/hn_readers/
18:42:25*vendethiel quit (Ping timeout: 264 seconds)
18:42:40BlaXpiriti probably wouldn't consider nim if it was mandatory
18:43:55keypusherdoes either one have to be mandatory though? can't you just resolve uglyCase and ugly_case to different things and let the writer choose?
18:44:20BlaXpiritare u serious
18:44:28BlaXpiritdid u even think before saying that?
18:44:29keypusherthat's the way other languages work
18:44:37*vendethiel joined #nim
18:44:44*ddl_smurf joined #nim
18:44:53keypusheryou resolve the actual name
18:45:25keypushermaybe im wrong
18:45:51ddl_smurfhello all – just read http://nim-lang.org/news.html#Z2015-04-30-version-0-11-0-released – very exciting news – wanted to ask: does this mean the GC is truly optional to the stdlib now ? are macros that need allocations robust ?
18:46:02ArrrrrrNot because blax writes half of the wrappers out there and you'd be forced to write_like_this
18:46:24BlaXpiriti wrote just 1 :|
18:48:09Arrrrrrhttps://github.com/BlaXpirit?tab=repositories
18:48:11boydgreenfieldDoes anyone know the underlying bug behind this commit changing the CountTables implementation? https://github.com/Araq/Nim/commit/5fbcf93860e68d7ddde4b01aa4b7222a7fcaaabc. Unfortunately, it appears to have broken `[]=` (and maybe more) in v0.11 for me. https://github.com/Araq/Nim/issues/2625 provides reproducible example.
18:49:06dom96ddl_smurf: A lot of stdlib procedures still use the GC. You will get warnings when you use them if you specify --gc:none though.
18:49:43ddl_smurfhey dom96, long time - does that mean --gc default to boehm now ?
18:49:45ArrrrrrYou have nim-chipmunk, nim-csfml
18:49:54ArrrrrrWell, 2.
18:50:19dom96ddl_smurf: indeed, welcome back. Nope, --gc still defaults to Nim's GC.
18:50:36ddl_smurfty
18:52:25keypusherBlaXpirit: perhaps i worded that poorly. i meant let the writer of the library choose which style they prefer (which they already can today), the caller would get whatever they call explicitly, with no magic insensivity
18:58:06ArrrrrrI have made some test with nims.cfg in windows xp. Using this works: p:".\\path\\to" but not this: p:"./path/to" which indeed works when passed directly to the compiler.
18:58:13*Jesin quit (Quit: Leaving)
19:02:41*iamd3vil quit (Ping timeout: 265 seconds)
19:06:02Araqkeypusher: that only trades one set of problems for another. I don't want to use foo_bar just because its author liked that style. I don't and I don't see the reason why it should matter in the first place.
19:06:02*vendethiel quit (Ping timeout: 264 seconds)
19:06:59AraqNim generally assumes the library writer is as much of an idiot as its consumer. Which I personally found completely true.
19:08:47Araqboydgreenfield: well that's quite possible. there is only so much we can test before a release
19:08:52*OnO quit (Quit: Textual IRC Client: www.textualapp.com)
19:11:42Araqand it may surprise you but *consistent spelling has no correlation whatsoever with software quality or the number of bugs". it's simply irrelevant and it would be nice if programmers could finally -after decades! - distinguish between syntax and semantics.
19:12:43AraqI cringe everytime I read an article like "Quake's code is awesome and here is why: It uses spaces after ("
19:12:58BlaXpirito.o
19:13:46*boydgreenfield quit (Quit: boydgreenfield)
19:21:04ArrrrrrNow i see why it was called nimrod *wink*.
19:21:13*xcombelle joined #nim
19:24:25*gsingh93 quit (Ping timeout: 264 seconds)
19:34:00*Varriount joined #nim
19:35:36*OnO joined #nim
19:36:11*BlaXpirit_ joined #nim
19:36:33*Varriount__ quit (Ping timeout: 256 seconds)
19:37:42*BlaXpirit quit (Ping timeout: 276 seconds)
19:38:03*BitPuffin|osx joined #nim
19:40:22*BlaXpirit-UA joined #nim
19:41:36*BlaXpirit_ quit (Ping timeout: 276 seconds)
19:41:54*elbow_jason2 is now known as elbow_jason
19:43:30*OnO quit (Quit: My iMac has gone to sleep. ZZZzzz…)
19:43:40*BlaXpirit joined #nim
19:44:40*Jesin joined #nim
19:45:29ArrrrrrI have to go, again, congrats for the release.
19:45:32*Arrrrrr quit (Quit: Page closed)
19:45:38*BlaXpirit-UA quit (Ping timeout: 272 seconds)
19:48:27*BlaXpirit quit (Ping timeout: 256 seconds)
19:49:53*BlaXpirit joined #nim
19:53:53*boydgreenfield joined #nim
19:54:50boydgreenfieldAraq: Not a critique, I get that these things happen. It’s just that in order to make a PR with a fix, it’d be helpful to understand why the breaking commit was originally made (i.e., what did it fix) – and I was/am having trouble figuring that out.
19:55:01*BlaXpirit quit (Ping timeout: 264 seconds)
19:55:20*thotypous quit (Ping timeout: 252 seconds)
19:58:42*BlaXpirit_ joined #nim
19:59:32*thotypous joined #nim
20:01:05*flaviu joined #nim
20:01:53flaviuCongrats on the release! I've been too busy to keep up lately, but it looks like there's lots of good stuff in there!
20:02:13*BlaXpirit-UA joined #nim
20:03:45*BlaXpirit_ quit (Ping timeout: 256 seconds)
20:07:24*Kingsquee joined #nim
20:08:48*xcombelle quit (Quit: Leaving)
20:12:08*vbtt_ joined #nim
20:12:10*Demos_ joined #nim
20:12:23vbtt_woohoo - congrats guys!
20:13:05*vendethiel joined #nim
20:13:09Araqah vbtt_ wb
20:15:00*vbtt_ quit (Client Quit)
20:15:34*Demos quit (Ping timeout: 255 seconds)
20:16:42*shodan45 quit (Quit: Konversation terminated!)
20:17:11*Demos_ quit (Read error: Connection reset by peer)
20:32:09*brson joined #nim
20:33:48Araqhey ddl_smurf welcome back
20:35:01*vendethiel quit (Ping timeout: 250 seconds)
20:37:10*shodan45 joined #nim
20:44:16ddl_smurfhey araq =)
20:46:23fowli thought add() was supposed to handle nil string :/
20:48:37vikatoncongrats on 0.11
20:48:47Araqfowl: turned out to be harder to implement than I expected it to be.
20:49:04Araqso it was delayed for 0.12.0
20:49:19fowlAraq, told you :p i had to move things around and the order was impossible iirc
20:49:56Araqvikaton: thank you :-)
20:50:42*HakanD___ joined #nim
20:51:03Senketsuomedeto for .11
20:51:10*boydgreenfield quit (Quit: boydgreenfield)
20:51:35vikatonmy 2 favorite languages both released new versions on the same day
20:52:07vikatonwhat a cool coincidence
20:52:10ddl_smurf+1 congrats to yall =)
20:52:53Araqvikaton: what is the other language? ;-)
20:53:18vikatonAraq, Crystal releases version 0.7.0 just minutes ago :P
20:53:20*BlaXpirit joined #nim
20:53:27vikatonreleased*
20:54:11*BlaXpirit-UA quit (Ping timeout: 256 seconds)
20:57:02*BlaXpirit_ joined #nim
20:58:08Araqaye
20:58:18*BlaXpirit quit (Read error: Connection reset by peer)
21:01:15*BlaXpirit-UA joined #nim
21:02:20*BlaXpirit_ quit (Ping timeout: 246 seconds)
21:02:44*Kingsquee quit (Ping timeout: 245 seconds)
21:04:43*BlaXpirit joined #nim
21:05:20*vbtt_ joined #nim
21:05:31*ingsoc quit (Ping timeout: 255 seconds)
21:05:43*vendethiel joined #nim
21:05:56fowlsomeone set this up please https://github.com/nim-lang/packages/pull/139
21:06:05*BlaXpirit-UA quit (Ping timeout: 256 seconds)
21:06:28fowlif nim lang has a travis ci token pm it to me ill set it up
21:08:43*vbtt_ quit (Client Quit)
21:09:29*BlaXpirit quit (Ping timeout: 256 seconds)
21:10:19*BlaXpirit joined #nim
21:11:03*mpthrapp quit (Remote host closed the connection)
21:13:15*Nub joined #nim
21:13:38*Nub is now known as Guest3414
21:13:55Guest3414Hi, i'm getting a type expected error from this
21:13:56Guest3414 var pixelArray: array[1..5 , GLfloat] glReadPixels( x,y-1, 1,1, GL_RGBA, cGL_FLOAT, ref pixelArray[0])
21:13:59Guest3414and i don't know why
21:14:43Guest3414the error persists even if change teh line to glReadPixels( x,y-1, 1,1, GL_RGBA, cGL_FLOAT, ref pixelArray)
21:15:43*BlaXpirit quit (Ping timeout: 256 seconds)
21:16:06Araq'ref' is only a type constructor
21:16:10fowlyou mean addr instead of ref
21:16:14Araqyou want 'addr' or something
21:16:34*BlaXpirit joined #nim
21:21:09Guest3414It changed there error, but it is expecting pointer instead of ptr
21:26:55Guest3414Malformed some other part of the code. Fixed it. Thanks guys
21:27:45*filcuc joined #nim
21:28:35*vendethiel quit (Ping timeout: 244 seconds)
21:31:48*HakanD___ quit (Quit: Be back later ...)
21:37:00*DKordic joined #nim
21:37:48Araqhi DKordic welcome
21:40:44DKordicAraq: Hello. +1 for making clear distinction between 'proc' and 'fun'.
21:44:48*gsingh93 joined #nim
21:44:57*filcuc quit (Ping timeout: 240 seconds)
21:45:08*nande joined #nim
21:45:59AraqDKordic: he, thanks.
21:46:39DSADFFFDDDDis there a way to change the default float literal to float32 for a scope, either with a pragma or a macro? its a pain in the ass to write 'f32 everywhere in opengl code :P
21:47:36DSADFFFDDDDi mean 'existing macro' not if its 'possible'
21:48:42fowl[1f32, 0,1,2] # array of float32
21:49:02fowlits not that bad
21:49:16Araqfowl: but it's hardly known ;-)
21:50:08*filcuc joined #nim
21:51:50DSADFFFDDDDnice that fixes most of the pain thx
22:07:51*BlaXpirit_ joined #nim
22:08:25*BlaXpirit quit (Ping timeout: 256 seconds)
22:12:38*BlaXpirit-UA joined #nim
22:13:23*BlaXpirit_ quit (Ping timeout: 250 seconds)
22:17:04*BlaXpirit-UA quit (Ping timeout: 255 seconds)
22:17:57def-Araq: any idea how i would best rename main to SDL_main? It also doesn't like the environment args at the end
22:18:22*BlaXpirit-UA joined #nim
22:19:10*DSADFFFDDDD quit (Ping timeout: 246 seconds)
22:20:13def-I can just change it in the resulting C file and it works, so I tried --noMain and emitting an SDL_main manually, but that ends up at the wrong position
22:20:41*Kingsquee joined #nim
22:20:58fowlinclude sdl_main.h
22:21:44fowlactually i never figured this out for sdl2 and nobody ever cared enough to implement it. the only platform it matters is osx iirc
22:21:58def-I'm compiling to Android and have this problem
22:22:18fowlyglukhov has resources for that
22:22:24*BlaXpirit joined #nim
22:22:25def-i know, but they looked complicated
22:22:33def-what I have looks much simpler now
22:22:44def-and works perfectly except for this small detail
22:23:16ddl_smurfthe small detail of not having a main ?
22:23:41def-yep, which I could fix by running sed over the C file but that feels so ugly
22:23:43*BlaXpirit-UA quit (Ping timeout: 256 seconds)
22:24:17def-fowl: doesn'
22:24:22def-t work for me
22:24:23Araqdef-: .emit allows you to specify a section
22:24:38Araqcheck it out, it's new, in 0.11.0 and documented
22:25:03yglukhovdef- https://github.com/yglukhov/nimx/blob/master/nimx/linkage_details.nim
22:25:16yglukhovand --noMain to nim
22:25:43Araqand it's also not listed in our news ...
22:26:06def-Araq: and I always read the old docs becuase i have them all bookmarked and google indexes them
22:26:47Araqwhat lol? google should index the new stuff hours ago
22:26:55Araq*should have indexed
22:27:06def-yglukhov: thanks, that worked
22:27:07*BlaXpirit quit (Ping timeout: 256 seconds)
22:27:22yglukhovwelcome =)
22:27:32def-Araq: but the old sites all still exist and are much higher up in the results
22:27:44def-i think they should redirect to 0.11.0 at least
22:29:34Araqwell I prefer to delete them
22:30:09ddl_smurfthen perhaps remove the version from the url ? i think google won't see them as updates otherwise
22:33:22*Jehan_ joined #nim
22:56:05def-http://hookrace.net/blog/nimes/
23:01:28*filcuc quit (Quit: Konversation terminated!)
23:04:51fowldef-, pretty cool
23:05:36fowlhow long were you working on this?
23:05:44*vbtt_ joined #nim
23:06:38def-Hm, I don't remember (and I threw away the git history because it consisted of thousands of "update" commits) Maybe dom96 remembers
23:06:47*yglukhov quit (Quit: Be back later ...)
23:06:53def-I started after I found out his GB emulator was much further than mine already
23:07:09fowlwas justa bout to ask
23:07:40fowlcan the emu run GB and NES games?
23:07:49def-Nope, only NES
23:07:58def-But first I wanted to make a GB emu
23:12:53def-20 days
23:13:35*Jesin quit (Quit: Leaving)
23:13:42*vbtt_ quit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
23:13:46def-Much longer than my usual Nim projects, which always took one night or one weekend at most
23:16:21*Jesin joined #nim
23:18:49*vbtt_ joined #nim
23:20:00*DSAFDSGFD joined #nim
23:25:06*JinShil quit (Quit: Konversation terminated!)
23:26:29*vendethiel joined #nim
23:29:12*vbtt_ quit (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client)
23:33:48*Trustable quit (Quit: Leaving)
23:42:12fowldef-: you going to do sound
23:46:22def-fowl: sound works, just not on android and js
23:47:34*vendethiel quit (Ping timeout: 244 seconds)
23:48:09*vbtt_ joined #nim
23:50:11*[dee] quit (Quit: WeeChat 1.1.1)
23:51:02*vbtt_ quit (Client Quit)