<< 28-08-2014 >>

00:02:12*Skrylar joined #nimrod
00:10:00*enquora quit (Quit: enquora)
00:16:42*Sht0 quit (Ping timeout: 260 seconds)
00:16:44*jjap quit (Quit: Page closed)
00:22:45*enquora joined #nimrod
00:56:49*Triplefox joined #nimrod
01:00:45VarriountSo, my first assignment in CS 202 was to model a vending machine. In Java.
01:01:22VarriountAll the while, I was going "why can't this bloody language be more like Nimrod!?"
01:01:48reactormonkVarriount, and that's why I didn't go into CS.
01:02:13reactormonkVarriount, you could also write it in scala. Less pain, more gain.
01:07:05Triplefoxback when i took cs i did a python version first
01:07:21Triplefoxthen the java
01:20:55*q66 quit (Quit: Leaving)
01:39:43VarriountTriplefox, reactormonk: We have no choice but to write in java
01:40:03VarriountIt's not the assignment itself that was hard/difficult, it's the language.
01:40:04reactormonkVarriount, and that's why I went for NLP instead of CS ^^
01:40:09VarriountNLP?
01:40:26reactormonkgo wikipedia.
01:49:19Skrylarmeep
01:50:00SkrylarVarriount: a friend sent me this one link to a guy who did an analysis on reddit; measured how many times language users reference other language, how often they curse and such
01:50:18Skrylarapparently LISPers were the most likely to say something was awesome and PHP was most likely to call something shitty
01:50:33SkrylarJava was pretty low on the list of people who were 'cheery' xD
02:26:16Skrylarhmm
02:26:59Skrylari guess i should figure out the benchmarking routines; trying to figure out if its worth replacing four multiply+add's per call with a branch that avoids it at the cost of having to flip the flag on occasion
02:27:10Skrylarnaivety says yes
02:27:55Varriountreactormonk: I actually thought about doing the assignment again in Nimrod, just to see how much the solutions compared.
02:32:20*enquora quit (Quit: enquora)
02:33:54*brson quit (Ping timeout: 255 seconds)
02:35:13SkrylarVarriount: i donno; was it a complex vending machine?
02:36:58VarriountSkrylar: Nah, just a lesson in object oriented components, serialization, simulation, and some other things
02:38:14OrionPKis that new async stuff working in devel?
02:38:27VarriountOrionPK: Yeah, sorta
02:40:21OrionPKim getting a compile error
02:40:30OrionPK'cb' is not gc safe
02:40:40OrionPKjust trying to do a basic http client
02:41:53SkrylarVarriount: likely not much different then; sometimes there's a minimum of complexity sadly
02:42:05Skrylarit doesn't get simpler than struct foo {} or (defstruct ())
02:43:20Skrylari think the difference only comes in when one starts getting to where abstractions help, because then you can start leveraging templates or macros whereas java simply is unable to do it
02:44:06VarriountAt least in Nimrod I don't have to create 3 different objects just to serialize something to a file.
02:45:38Varriountnew ObjectReader(new BufferedReader(new FileReader(fileName)));
02:48:11*andreysh joined #nimrod
02:48:52VarriountSkrylar: Here's a link to the source if you're interested - https://github.com/Varriount/CSC202-VendingMachine
02:51:48Skrylar:S serialization is something i'm hiding from atm
02:52:00Skrylarstill have to finish and debug that msgpack v5 crap
02:52:32VarriountMan, where do you find the time for all this stuff?
02:52:34SkrylarVarriount: i see you have the requisite boilerplate... lol
02:53:13Skrylari love manually keeping track of the whole fopen() {...} flush() close() crap when lispers have (with-file)
02:53:16VarriountPrintWriter writer = new PrintWriter(new BufferedWriter(new FileWriter(
02:53:16VarriountfileName, true)));
02:53:31*Varriount starts crying
02:53:34Skrylarbut don't forget the like 10 lines of try/catch/else to make sure you don't leak a file
02:53:38Skrylarwhen lispers still have (with-file)
02:53:40Skrylarlol
02:54:03VarriountAnd the pythonista have 'with open() as fh'
02:54:11Skrylartechnically nimrod can have withFile(): ... because block statements are allowed in templates
02:55:31Skrylari think its possible to do a template that does the whole "if error, close file and reraise" thing
02:56:38VarriountThe main thing I have against java is that is pretty much requires an IDE if you want to be productive in it.
02:57:05VarriountWhereas with Nimrod or Python, I can pretty much code things on my phone if I have to.
02:57:07Skrylarthats true of lisp and a few others though
02:57:11Skrylarwell
02:57:18Skrylari guess its not strictly true but they help
02:57:35Skrylarits just weird because usually half of what a Java IDE does is already available in a lisp image
02:58:07Skrylarits easy to just ask SBCL to put debug tracers in system functions; java requires some big enterprise crap and training to do the same
03:00:04*saml_ joined #nimrod
03:00:29*vegai quit (Ping timeout: 272 seconds)
03:01:22SkrylarVarriount: what gets really insane is when you start using org-mode to program
03:01:44Skrylarbecause org-mode tables have an 'export' function, so you can have it spit data tables out to C/assembly/blah
03:02:12Skrylartoss magic numbers in table, let it run spreadsheet commands, export to program code, tangle in to project files. @_@
03:06:45*andreysh quit (Quit: Page closed)
03:06:52*vegai joined #nimrod
03:48:23*xenagi quit (Quit: Leaving)
03:56:30*kshlm joined #nimrod
04:39:33*nande quit (Read error: Connection reset by peer)
04:48:52*saml_ quit (Ping timeout: 240 seconds)
05:06:26*Sht0 joined #nimrod
05:54:21*seubert quit (Remote host closed the connection)
06:19:42*gkoller joined #nimrod
06:22:41*milosn quit (Remote host closed the connection)
07:48:17*BlaXpirit joined #nimrod
07:57:37*jbe joined #nimrod
08:00:21*jbe quit (Remote host closed the connection)
09:08:24*kunev joined #nimrod
09:08:40*Trustable joined #nimrod
09:18:50*io2 joined #nimrod
09:35:59*Matthias247 joined #nimrod
10:08:49*milosn joined #nimrod
10:31:47*EXetoC joined #nimrod
10:32:39*foodoo joined #nimrod
10:51:03*Sht0 quit (Ping timeout: 240 seconds)
11:03:54*kshlm quit (Ping timeout: 250 seconds)
11:15:54*foodoo quit (Remote host closed the connection)
11:48:22*kemet joined #nimrod
11:52:03*kemet quit (Client Quit)
12:45:00*saml_ joined #nimrod
12:53:46*darkf quit (Quit: Leaving)
12:55:10*milosn quit (Ping timeout: 264 seconds)
12:58:46*saml_ quit (Ping timeout: 264 seconds)
13:00:15*jasondotstar joined #nimrod
13:37:48*Sht0 joined #nimrod
13:47:56*milosn joined #nimrod
14:20:33*gkoller quit (Quit: Textual IRC Client: www.textualapp.com)
14:58:21*wan joined #nimrod
14:59:03wanHey all
14:59:14wanDoes anyone know the difference between cint and int?
14:59:39wanI'm finding it annoying to use 0.cint to use some wrappers...
15:11:17OrionPKtypically nothing, but IIRC it might vary by compiler/architecture
15:12:08wanBut what's an example case when it actually is different?
15:12:20*brson joined #nimrod
15:13:53wanWe only have one nimrod compiler, so if the 'int' nimrod implementation is backed by an 'int' in the generated c, there shouldn't be a case where nim'int and cint are different.
15:15:59*[CBR]Unspoken joined #nimrod
15:17:50*[CBR]Unspoken1 quit (Ping timeout: 260 seconds)
15:18:22wanWell, for procedure calls at least, int == cint (and the compiler doesn't complain when you give an int to a cint argument)
15:18:41wanThe problem is for tuples, this is not the case, you are forced to manually convert.
15:24:58wanReading the source of nimbase.h, I see that if we're in 64bits => typedef int64_t NI
15:25:23wanAnd if we're in 32bits => typedef int32_t NI
15:25:54wanIf C's ints have the same behavior, int and cint are redondant. We should only keep one.
15:28:33wanI guess it's because in C, there is no standard behavior for int size
15:28:41*kunev quit (Quit: Lost terminal)
15:29:20*gsingh93 joined #nimrod
15:30:45*gkoller joined #nimrod
15:53:45*mko joined #nimrod
15:56:49*Matthias247 quit (Read error: Connection reset by peer)
16:00:13*milosn quit (Ping timeout: 244 seconds)
16:05:20*nande joined #nimrod
16:06:37EXetoCint == cint? on what platforms? I assume you're witnessing an implicit conversion
16:06:51EXetoCwan: this tuple behavior might have been reported
16:06:58EXetoCif not, then it has at least been acknowledged
16:10:21EXetoCint is 32-bit on x86 and 64-bit on x86_64. cint deviates slightly on x86_64 at least, and probably on other platforms as well
16:11:14EXetoCso it's necessary to have the cint type as well as the other C types
16:11:25*io2 quit (Quit: ...take irc away, what are you? genius, billionaire, playboy, philanthropist)
16:11:56*io2 joined #nimrod
16:12:42*untitaker quit (Ping timeout: 246 seconds)
16:14:31wanYeah, that was my assumption, and my mistake. Just got bitten because I thought I could just rename cint to int in a wrapper. Dammit.
16:15:19wanThey ARE different, I just don't understand why there is the need for two.
16:15:52wanWhy can't typedef int NI ?
16:16:04EXetoCbecause nimrod's int is the largest signed integer, while it *might* be that in C, but often isn't
16:16:34EXetoCand nimrod's uint would be the largest unsigned integer of course
16:18:21*untitaker joined #nimrod
16:19:56wanI really thought that this was also the behavior of C. Unfortunately, on 64bits on my machine, sizeof cint == 32.
16:21:08wanSome of C's rules are strange (or annoying). It should be better defined.
16:22:24EXetoCC does have typedef's for fixed integer sizes though
16:25:32*Ven joined #nimrod
16:35:03*gkoller quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
16:50:58*johnsoft quit (Ping timeout: 264 seconds)
16:51:09*johnsoft joined #nimrod
16:53:25*milosn joined #nimrod
16:54:55*q66 joined #nimrod
17:10:39*wan quit (Quit: WeeChat 1.0)
17:15:12*gkoller joined #nimrod
17:19:54*johnsoft quit (Ping timeout: 246 seconds)
17:20:18*io2 quit (Quit: ...take irc away, what are you? genius, billionaire, playboy, philanthropist)
17:22:07*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
17:44:54dom96hi
17:45:14dom96OrionPK: did you fix it? if not can you gist what you tried?
17:50:56*Varriount is here for 10 minutes
17:52:34*Ven joined #nimrod
18:19:48*BlaXpirit quit (Quit: Quit Konversation)
18:21:23*BlaXpirit joined #nimrod
18:30:27*bramgg joined #nimrod
18:30:30*bramgg left #nimrod (#nimrod)
18:36:17*zahary joined #nimrod
18:46:42OrionPKdom96 nope, didnt figure it out
18:47:07OrionPKit's on my other machine, give me a minute..
18:48:54dom96Your proble is likely that you are trying to access a global from inside an async proc.
18:48:57dom96*problem
18:51:28dom96Araq: Thought of a better way to handle this gcsafe stuff yet?
18:53:55OrionPKah am doing that
18:54:02OrionPKI* am
18:54:05OrionPKthat must be it then
18:56:11*foodoo joined #nimrod
18:56:27dom96Yeah, we need to at the very least disable this gcsafe stuff when threads are not on.
19:09:23*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
19:10:07Araqdom96: well I notice that OrionPK's problem is not a lack of 'gcsafe' annotations
19:10:23Araqbut his problem is that what he does is in fact GC unsafe
19:11:35Araqso that doesn't really help in deciding if 'gcsafe' should be the default for proc types
19:11:49dom96it's safe when he's not spawning threads
19:14:08AraqI fear the real problem is that not even the main thread may access globals because we have no notion of 'main thread' in the type system
19:14:56Araqand now that I've written it down this way I have an idea ...
19:18:08*jjap joined #nimrod
19:22:17*Ven joined #nimrod
19:22:40jjapI created a mac installer package: http://forum.nimrod-lang.org/t/532
19:22:55Varriountjjap: Thanks!
19:22:59*Varriount pokes dom96
19:23:05jjapUninstalls, handles multiple versions, updates path cleanly/universally
19:23:22jjapVarriount: No problem :)
19:23:32Araqjjap: was about to thank you. however does it also handle multiple versions when the new version has a new name?
19:23:56jjapAraq: What do you mean by new name?
19:24:11Araqwe're renaming nimrod to nim
19:25:02jjapAraq: It'll work
19:25:08Araqyay
19:25:22foodoonot a joke? nimrod -> nim?
19:25:22Araqdom96: ok, there is a way to make it work, but you won't like it
19:26:12OrionPKyay!
19:26:13OrionPKnim :)
19:26:54*Ven_ joined #nimrod
19:27:22*Ven quit (Ping timeout: 245 seconds)
19:27:33Araqdom96: if 'gcsafe' implies "cannot use createThread/spawn" we can allow the implicit transition takesGcSafe(gcUnsafeProc)
19:27:43Araq(I think!)
19:28:20Araqthis means stuff "simply works" as long as you can't use 'spawn' in your dispatcher
19:28:39Araqwhich is ... meh
19:29:31dom96foodoo: yes
19:29:41dom96Varriount: yes?
19:29:46dom96jjap: great job!
19:30:06Araqwe can go further than that if we do not conflate gcsafety with "spawnability", but then we get {.gcsafe, nospawn.} everywhere or something like that
19:30:22dom96Araq: Well I don't really get what you mean.
19:30:46jjapAraq: Caveats: Is it ok that old versions keep old (symlink) names? example: ./nimrod-0.9.4 but ./nim-1.0.2 ;; And, is it ok that ./nimrod will point to the last version that used that name?
19:31:15Araqjjap: sure. that's how it should be done.
19:31:31jjapdom96: Thank you
19:31:37dom96Regarding installers/packages, we should document exactly what should be in a package on the wiki.
19:31:53dom96Perhaps list the release steps too.
19:32:02dom96Things we should check before we release etc
19:32:55Araqdom96: it's hard for me too
19:33:13*foodoo wonders why "nim" should be preferred over the much nicer "nimrod"
19:33:36Araqfoodoo: americans think nimrod means idiot
19:34:27foodooWell, git is a popular software, isn't it?
19:34:47Araqyes, but I'm not Linus
19:34:49jjapThe multiple-versions feature of my installer, though it works well, is an extra: If people want a crossplatform nimrod installer/version-manager, it could be written in nimrod in the style of something like ruby-install
19:35:22foodooI'm sure this has been discussed elsewhere but I don't think that you should give up a perfectly fine name just because people are stupid
19:36:19Araqfoodoo: I'm also not Simon Peyton Jones and so my TR macros are an obviously stupid idea, never mind Haskell does the same and gets no blame for it
19:37:07Araq;-)
19:38:47Araqfoodoo: but seriously 4 out of 5 people appreciate a name change and it can't hurt to care somewhat more about popularity
19:39:28dom96foodoo: You are in fact the first person to react negatively to the name change I think.
19:39:50jjapI didn't think any programmers were distracted by the name.
19:39:55dom96In any case, wearing a Nimrod t-shirt in America would make me feel uncomfortable.
19:40:08jjapBut I guess i like history :)
19:40:21Demosdom96, good point
19:40:25Araqdom96: screw it, it doesn't work
19:40:31Araqit's not sound
19:40:32jjapTo be clear, we're talking about changing the programming language name? Or just the binary?
19:40:53Araqjjap: the language, the urls, the binary
19:41:45foodooWhat about Nimbus instead?
19:42:03Araqdom96: argh, it does work but it's more complicated ...
19:42:46*Francisco joined #nimrod
19:43:06Araqseriously ... this is too complex, let's go with --threadAnalysis:off as the default
19:43:15dom96Araq: It's your choice. But if OrionPK stumbles upon this then everyone else will too.
19:43:33dom96And I will remove gcsafe from the async stuff because otherwise people will think it's inferior.
19:43:48Araqwhat? you can't do that!
19:44:35Araqfoodoo: we kept the decision to Nim vs Nimrod in order to come to a conclusion
19:45:06jjapAraq: You mean Artaxerxes or Darius The Great (Language) is not being considered?
19:45:09*Fr4n quit (Ping timeout: 240 seconds)
19:45:16dom96Araq: threadAnalysis should be on when threads are on
19:45:18foodooWell, you are the BDFL, so it's your decision
19:45:21dom96Araq: It's simple no?
19:45:50UNIcodeXi came across it just fine.
19:45:55UNIcodeXi like the name
19:45:56Demosdom96, if I write a whole big application and then want/need to add threads I don't really want to have to fix all kinds of thread analysis issues
19:45:58UNIcodeXstands out
19:46:09foodooUNIcodeX: You mean Nimrod or Nim?
19:46:13UNIcodeXnimrod
19:46:13Araqdom96: yes. it is that simple except that we don't know yet what problems that will cause
19:46:42*enquora joined #nimrod
19:46:46foodoohttp://www.merriam-webster.com/dictionary/nimrod It's actually in the dictionary as an insult :-/
19:46:47UNIcodeXi forgot how i found it thou.... <--- ponders
19:46:52dom96Demos: If I never intend on using threads then I don't want to worry about gcsafe.
19:47:00UNIcodeXwell, yea... but who cares
19:47:01UNIcodeXlol
19:47:16Araqwell since I think they should rename Go and D and perhaps Rust too, it's only fair I rename my own language :-)
19:47:19dom96Demos: If you are writing a big app with the intention of using threads in the future then just enable thread analysis while developing.
19:47:36foodooGo and D are nice puns imho
19:47:40UNIcodeXa nimrod... synonymous with a 'tool' and what better name for a language than a synonym of 'tool
19:47:55dom96I'll also rename Babel to Nimble btw
19:48:37OrionPKi like that name too
19:48:38OrionPK:)
19:48:54UNIcodeXOrionPK: nimble or nimrod?
19:48:55jjapNim is apparently an ancient game... https://en.wikipedia.org/wiki/Nim
19:48:58foodooNimble clearly has a positive connotation
19:50:01EXetoCnimla.ng
19:50:35foodooThere should be a TLD for programming languages
19:51:25dom96jjap: Time to implement it in Nim! :D
19:51:33EXetoCnimlang.pl
19:51:46foodooEXetoC: good point
19:52:13UNIcodeXor just nim.pl
19:52:22jjapdom96: And tear the very fabric of space and time? You first.
19:52:29UNIcodeXrhymes with pimple though..... not good
19:52:31dom96As someone who is Polish I support this idea.
19:53:15dom96jjap: Not to worry, the doctor has our back.
19:53:59*foodoo quit (Quit: brb)
19:54:16EXetoCsilly documentaries made for prime-time tv. so dramatic
19:54:50*foodoo joined #nimrod
19:54:54dom96I wonder if we translated some docs to some other languages if that would give us an edge.
19:55:28foodoodom96: First make the syntax and the stdlib stable. Then write all the docs
19:55:55dom96foodoo: yeah... I need to get my priorities straight heh
19:56:58dom96Araq: any tips for fixing https://github.com/Araq/Nimrod/issues/1502 ?
19:57:18*Matthias247 joined #nimrod
20:01:15Araqdom96: sure, make defaultEventHandle 'nimcall' instead of 'closure'
20:01:31dom96Araq: can't, it's an async proc.
20:01:42jjapEXetoC: But if little sussie tries to eat that pie before it fully cools, she could suffer severe lip burns at temptures UP TO 450 DEGREES
20:01:47Araqit is a top level proc, so it cannot really be .closure, can it?
20:01:50dom96Araq: hrm, or maybe I can.
20:02:26dom96Araq: ahh, yeah. But I can't make the type nimcall.
20:02:36Araqwhy not?
20:03:07dom96because async generates a closure
20:03:08dom96I think
20:03:19dom96well, it can generate a closure.
20:03:30dom96maybe I could get away with it for now
20:04:45dom96interesting that it's not a problem for asynchttpserver
20:04:51dom96I guess it's a generics issue
20:05:04UNIcodeXoff topic... does anyone know of a good channel for becoming more proficient in German? a place where they don't mind answering questions and can communicate in English as well?
20:06:09dom96##german?
20:06:25dom96redirects to ##deutsch
20:11:03Araqdom96: I don't think it's related to generics
20:11:17Araqin fact I found this bug some weeks ago but considered it minor
20:11:28dom96what do you think it is then?
20:12:56Araqas I said, a top level proc annotated with 'closure'
20:13:04*gkoller quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
20:14:37dom96oh
20:14:40dom96interesting
20:14:50dom96that is minor then
20:15:45dom96shouldn't it be pretty simple to fix?
20:17:31Araqno, it's LL
20:18:44*EXetoC quit (Quit: WeeChat 1.0)
20:18:48UNIcodeXdom96: thanks but they seem to be empty... or i'm doing it wrong.
20:19:15dom96there is 90 people in ##deutsch
20:20:16UNIcodeXnevermind.... i was in the wrong server console window.
20:20:18UNIcodeXthanks
20:29:19*Mat3 joined #nimrod
20:29:23Mat3hello
20:30:02foodooMat3: greetings
20:31:05Mat3hi foodoo
20:31:15Mat3(interesting nick I must say)
20:32:22foodoothanks :)
20:37:22foodoo##french is also nice :D
20:44:54VarriountHm. Did I miss something?
20:45:12dom96Varriount: why were you poking me?
20:46:06Varriountdom96: jjap made an installer for Mac. Shouldn't it go somewhere... official?
20:46:09*jjap left #nimrod (#nimrod)
20:46:25*Varriount looks at the downloads page of the Nimrod website
20:46:50dom96true
20:47:11Mat3any news about the new website ?
20:47:30VarriountAraq: Anything for me to fix/help with/administrate?
20:48:23dom96Varriount: Write a wiki article that outlines the release steps (including the files a release archive must include).
20:49:15dom96Varriount: if you want something fun to do then write a starter pack for vindinium.
20:49:30Varriountdom96: I can write one for Windows, however I'd only be guessing at what steps would be needed on Posix/Mac
20:50:25Varriount(for the wiki article)
20:52:00dom96Varriount: I'm thinking something like this: https://github.com/kangax/fabric.js/wiki/Releasing-new-version
20:52:03dom96But with a bit more detail.
20:52:23dom96You don't need to worry about the commands that need to be executed for Linux/Mac.
20:52:46dom96Even if it's just for Windows it's a good start
20:56:15AraqVarriount: we plan to release this weekend. are you prepared?
20:57:15dom96That reminds me.
20:57:27dom96Argh. jjap left.
21:03:41AraqVarriount: please make terminal.nim use winlean and add the other requires stuff to terminal.nim directly, I want to get rid of windows.nim
21:03:55Araq*the other stuff it requires
21:04:06*foodoo quit (Quit: end of recursion)
21:11:06Mat3ehm, is terminal.nim a terminal emulator library (something like ansi.sys for MSDOS) ?
21:12:03*wan joined #nimrod
21:16:48AraqMat3: no, it simply adds colors to some console output
21:19:48*milosn quit (Ping timeout: 255 seconds)
21:20:38*enquora quit (Quit: enquora)
21:23:38BlaXpiritFinally collected everything I've been saying about random number generation into posts on forum and GitHub http://forum.nimrod-lang.org/t/533
21:24:23*enquora joined #nimrod
21:26:13AraqBlaXpirit: please elaborate? what do you mean "I had exactly these thoughts" wrt case (in)sensitivity?
21:26:44BlaXpiritI was imagining some stuff I would want from a perfect programming language
21:27:03BlaXpiritAnd I thought of having camelCase and under_scores being replaced into one another
21:27:15BlaXpiritbefore seeing this post on the forum which suggests this for Nimrod
21:27:37VarriountAraq: Will do.
21:27:55VarriountAraq: Prepared for a release? Yes.
21:28:26dom96Varriount: Clear your schedule on Sunday ;)
21:32:00*lojak joined #nimrod
21:32:06AraqBlaXpirit: aye, nice
21:32:06*lojak left #nimrod (#nimrod)
21:40:23dom96yay retrFile works
21:40:36*jhc76 joined #nimrod
21:52:59Araqwho want to migrate the wiki pages to https://github.com/Araq/Nim ?
21:53:19Araqargh
21:53:27AraqI could have renamed it instead?
21:53:42BlaXpiritwait... what is Nim?
21:53:45OrionPKyou still can
21:53:50OrionPKNimrod => Nim
21:54:05BlaXpirit..........
21:55:21dom96Araq: yes...
21:55:39dom96Don't create a new repo if that's what you're doing
21:56:08dom96and don't rename it until we have everything ready
21:56:29BlaXpiritreally don't see the point of this
21:56:46BlaXpiriti guess the decision is already made
21:57:21dom96BlaXpirit: This is the problem: http://www.reddit.com/r/programming/comments/2ed9ah/some_notes_on_d_for_the_win/cjyfqmq
21:57:43BlaXpiritdom96, I don't get it
21:58:38BlaXpiritthink of google
21:58:42BlaXpiritthink of broken links
21:58:43BlaXpiritgeez
21:59:54Triplefoxi support the change, now you can say "it's nim-ble" instead :D
22:00:52BlaXpirit50 place in google search will be nice
22:01:04BlaXpiritand it probably won't ever raise higher than 5
22:01:44*wan quit (Quit: WeeChat 1.0)
22:02:00BlaXpiritdom96, are you serious, did that one message lead to a rename?
22:03:03dom96no
22:03:10dom96I need to go to sleep
22:03:12dom96bye
22:04:48*Mat3 quit (Quit: Verlassend)
22:05:49AraqBlaXpirit: no, the real problem is that nobody understands the name
22:06:07BlaXpiritand "nim" is totally a word with a meaning
22:06:12BlaXpiritwhat do u mean "understand"
22:06:48BlaXpirit"nim" sounds so ... quiet. i can even imagine that it is awkward to say it
22:07:34BlaXpiritbut again... think of the position in the search engine and
22:07:41BlaXpiritit's almost like starting from scratch
22:07:43Triplefoxit'll be easy to get a high rank, much easier than competing against bible-spammy sites
22:08:13Araqwell even the few that understand the reference to the bible get it wrong, BlaXpirit
22:09:34Triplefox8 million results vs. 134,000,000
22:09:47Triplefoxhmm
22:10:23BlaXpiriti see nimrod 2M, nim 12.4M
22:10:51Triplefoxthese are all "n___ institute of management" acronym results though
22:11:19BlaXpiritwhich doesn't make it any better
22:13:08Triplefoxwell, i've seen what happened with haxe already. nicolas was stubborn, never changed, and to this day nobody knows how to pronounce it and keeps asking "you mean like hexidecimal"
22:13:36BlaXpiritpronunciation is not an issue here
22:14:20Triplefoxyeah, instead we have phbs going "are you saying we are going to code in a language for dummies"
22:14:51BlaXpirithuh
22:16:04*Varriount is neutral on the whole renaming-issue
22:16:40BlaXpiriti very rarely oppose change
22:16:44BlaXpiritbut i see only downsides
22:19:26AraqBlaXpirit: fwiw "Nimm" in Germans means "take"
22:20:36*enquora quit (Quit: enquora)
22:21:41BlaXpiritin context of my language it definitely sounds weird
22:22:01*tinAndi joined #nimrod
22:23:40BlaXpirito well
22:26:57AraqBlaXpirit: what is your mother tongue?
22:27:17BlaXpiritwhy does it matter? o.o
22:27:20BlaXpiritit's Ukrainian
22:29:21OrionPKdom96 how do you invoke an await and block until it's done?
22:29:23OrionPKerm
22:29:24OrionPKinvoke an async
22:29:37OrionPKis there a tutorial/guide somewhere?
22:30:37AraqOrionPK: you 'await' it?
22:30:45OrionPKwhen I call an async function w/o await I get : value of type 'PFuture[void]' has to be discarded
22:31:04OrionPKI can await all the functions until the "main", but then what?
22:31:27Araquse the dispatcher or you'll be in a world of trouble
22:31:46Araqsee some async module's isMainModule section
22:31:56OrionPKah see thats what's missing from the example on here: http://nimrod-lang.org/news.html#Z2014-04-21-version-0-9-4-released
22:32:30Araqwell sorry you can't learn async+await from the news announcement alone :P
22:32:52OrionPK:P
22:32:57OrionPKim just saying.. a tutorial would be good
22:33:09Araqhe wrote a blog post about it
22:33:12OrionPKdont see one up here: http://nimrod-by-example.github.io/
22:33:20OrionPKis that linked in the announcement?
22:33:47Araqwell release 0.9.4 was a disappointment for everybody anyway
22:34:03*wan joined #nimrod
22:34:36OrionPKdont see anything here about async/await http://picheta.me/
22:34:56OrionPKim not disappointed really... i've just been out of the loop for the past few months
22:35:14*Trustable quit (Quit: Leaving)
22:35:56Araqhu? I guess he never released the blog post
22:36:16Araqperhaps I told him to wait until it's stable
22:36:22OrionPKhehe
22:36:49OrionPKi just want to write an application that awaits a couple operations and then exists
22:36:50OrionPKexits*
22:47:56OrionPK"Future already finished, cannot finish twice." this should not be an error
22:48:12OrionPKif the future is already complete it should just call the complete function
22:48:42OrionPKthats how it works in JS/C# anyway
22:52:34*q66[lap] joined #nimrod
22:52:34Araqwell dom96 is sleeping, but I agree with you
22:53:06*q66[lap] quit (Changing host)
22:53:06*q66[lap] joined #nimrod
22:55:12*tinAndi quit (Quit: ChatZilla 0.9.90.1 [Firefox 31.0/20140716183446])
22:57:18*BlaXpirit quit (Quit: Quit Konversation)
23:01:14*darkf joined #nimrod
23:01:35Matthias247OrionPK: you should only be able to complete it one time. But you probably should be able to attach more than one continuation to it
23:13:23*bogen joined #nimrod
23:17:01*dom96 quit (Excess Flood)
23:18:44*q66[lap] quit (Quit: My MacBook Pro has gone to sleep. ZZZzzz…)
23:19:58*dom96 joined #nimrod
23:22:42reactormonkVarriount, add them to nimrod by example
23:30:44Skrylar@earlier i don't have a massive issue with the de-prefixing (I don't see the point, it solves the stupid "foo = Foo" by making it "foo = TFoo()") but if i see case sensitivity get flipped on I will build a prison shank
23:35:09*Ven_ quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
23:53:41*brson quit (Quit: leaving)
23:58:51*Boscop joined #nimrod