<< 24-12-2014 >>

00:01:28*bjz quit (Ping timeout: 255 seconds)
00:08:52*jefus_ joined #nim
00:12:16*jefus quit (Ping timeout: 255 seconds)
00:29:06Araqflaviu: seems I can't make #1678 to work and at the same time retain parsing sanity
00:30:31*candlefactory quit (Ping timeout: 252 seconds)
00:30:37Araqthing is, we also want to allow 1-liners for 'try'
00:31:43flaviuMight as well leave it open, it's not particularly important anyway
00:32:08Araqand we don't want to ignore indentation completely either
00:32:20Araqas then nesting becomes fishy:
00:32:25Araqp(
00:32:27Araq try:
00:32:38Araq try:
00:32:46Araq except ValueError:
00:33:07Araq except IOError: # belongs to innermost 'try' then?!
00:33:17Araqhowever
00:33:28flaviudidn't you get rid of significant comments ?
00:33:35AraqI did
00:33:39Araqnot the point here
00:34:03Araqlook at my above example
00:34:22flaviuHow could except IOError belog to the innermost try?
00:34:28Araqthe rule you're after here is "align 'except' to the 'try'"
00:34:48Araqbut the current grammar has no such concept and no such rule
00:34:52ldleworkouch
00:35:11ldleworknot even like, with if's and elses'
00:35:13ldlework?
00:35:33Araqand I don't want to add a rule like that either
00:35:44ldleworko.O
00:35:56AraqsomeLongLine(case x
00:36:07Araq of foo: .... )
00:36:34Araq'of' doesn't need to be aligned to the 'case' here
00:36:50flaviuisn't the grammar like `<try expresison> ::= 'try' ':' IND <statement>+ DED 'except' ':'`?
00:37:07flaviu`<try expresison> ::= 'try' ':' <statement> 'except' ':'`
00:37:29flaviuoops, forgot the trailing <statement> on both.
00:38:40Araqthat is for the try statement, but we're talking about the try expression
00:39:13flaviuThere's a difference?
00:40:34Araq.eval try: echo("hi") except: echo("ho")
00:40:37MimbusAraq: hi
00:42:21Araqyeah there is a difference but I'm not sure if it's truely necessary
00:44:52Araqhrm but maybe we should really consider to go with the "alignment" rule
00:50:24Araqoh well
00:50:25*saml_ joined #nim
01:04:49*yglukhov joined #nim
01:05:11*z1y joined #nim
01:06:29*nimnoob__ quit (Ping timeout: 245 seconds)
01:09:01*yglukhov quit (Ping timeout: 244 seconds)
01:11:49*z1y quit (Remote host closed the connection)
01:12:11*z1y joined #nim
01:20:21dom96Araq: In that case perhaps the 'of' should be aligned to the /ca
01:20:26dom96*'case'
01:20:40Araqyes, but this is not how it currently works
01:21:12dom96In the interest of expressiveness #1678 should work.
01:21:16Araqand I won't change it for 1.0. breaks code, gain is questionable at best
01:21:39Araqexpressiveness has not much to do with layout restrictions
01:22:12dom96Is there a different way to use 'try' as an expression like that?
01:24:24*kniteli quit (Ping timeout: 245 seconds)
01:24:35Araqas a one-liner
01:24:46Araqwhich is the more important use case anyway, IMO
01:25:14EXetoCwell what's the purpose if you can't return a value?
01:25:19EXetoCthough I did report that
01:26:10dom96So, why does an if expression work in that case but not a try expression?
01:26:29EXetoCno wait
01:26:48Araqdom96: an 'if' expression doesn't work either
01:27:29Araq'case' does but then there is no "inline case" where the 'of' is in the same line
01:27:37EXetoCno it's about using any block containing a raise as an expression
01:27:58AraqEXetoC: you speak of something completely different
01:28:33dom96Araq: It does without parenthesis though.
01:28:44Araqyes.
01:28:57dom96As does the try expression.
01:29:29dom96That's fine I guess.
01:35:02*z1y quit (Ping timeout: 258 seconds)
01:51:38*z1y joined #nim
01:56:19*z1y quit (Ping timeout: 264 seconds)
02:05:39*Boscop_ quit (Ping timeout: 245 seconds)
02:15:13*flaviu quit (Remote host closed the connection)
02:19:32*jwhisnant joined #nim
02:20:07*jwhisnant left #nim (#nim)
02:28:51*darkf joined #nim
02:33:40*dom96__ quit (Read error: Connection reset by peer)
02:40:02*flaviu joined #nim
02:47:04*kapil__ joined #nim
02:53:32*yglukhov joined #nim
02:57:43*yglukhov quit (Ping timeout: 244 seconds)
02:59:19*bjz joined #nim
03:10:29*dyu joined #nim
03:25:49*nimnoob__ joined #nim
03:32:00*haldean joined #nim
03:34:06haldeanHey folks! I'd love to start hacking on nim and I noticed that constants like "4." are parser errors, instead of being parsed as floats
03:34:29haldeanThat seemed like (a) not desirable behavior and (b) something probably fixable with a little change
03:34:38haldeanWould a patch that caused "4." to parse as a float constant be welcome?
03:35:18dyu4.float
03:36:45haldeansure, I know you can get around it
03:37:09haldeanin many (most?) other languages, adding a period onto a base-10 integer literal promotes it to a float literal
03:37:23haldeanmostly I'm wondering if that behavior would be desirable for nim
03:38:10dyuor you can: type f = float ... they use 4.f
03:38:15dyuthen*
03:38:33*z1y joined #nim
03:46:20*z1y quit (Remote host closed the connection)
03:47:20*z1y joined #nim
04:11:17*shadowe989 joined #nim
04:14:56*BitPuffin quit (Ping timeout: 264 seconds)
04:16:41*z1y quit (Quit: Leaving.)
04:17:17haldeanquit
04:17:19*haldean quit (Quit: leaving)
04:17:34*z1y joined #nim
04:42:26*yglukhov joined #nim
04:43:57*ehaliewicz joined #nim
04:46:32*yglukhov quit (Ping timeout: 245 seconds)
04:47:23*nimnoob__ quit (Ping timeout: 265 seconds)
04:58:27*saml_ quit (Ping timeout: 272 seconds)
05:11:37*BitPuffin joined #nim
05:14:24*kniteli joined #nim
05:15:57*BitPuffin quit (Ping timeout: 240 seconds)
05:42:47*vendethiel quit (Ping timeout: 245 seconds)
05:46:34*khmm joined #nim
05:52:52*vendethiel joined #nim
06:00:52*dts|pokeball quit (Ping timeout: 240 seconds)
06:04:21*kniteli quit (Read error: Connection reset by peer)
06:20:35*yglukhov joined #nim
06:22:58*BlaXpirit joined #nim
06:23:52*starless joined #nim
06:24:52*yglukhov quit (Ping timeout: 245 seconds)
06:25:37*BitPuffin joined #nim
06:27:12*loz1 joined #nim
06:30:32*BitPuffin quit (Ping timeout: 264 seconds)
06:33:58*z1y quit (Ping timeout: 256 seconds)
06:34:05*starless quit (Quit: WeeChat 0.4.2)
06:39:55*z1y joined #nim
06:41:21*loz1 quit (Quit: Leaving.)
06:44:51*z1y quit (Ping timeout: 272 seconds)
06:47:52*shadowe989 quit (Ping timeout: 240 seconds)
06:49:07*shadowe989 joined #nim
06:49:10*shadowe989 quit (Max SendQ exceeded)
06:50:20*shadowe989 joined #nim
06:50:27*shadowe989 quit (Max SendQ exceeded)
07:00:30*shadowe989 joined #nim
07:00:37*shadowe989 quit (Max SendQ exceeded)
07:01:53*shadowe989 joined #nim
07:02:15*shadowe989 quit (Max SendQ exceeded)
07:02:38*shadowe989 joined #nim
07:02:45*shadowe989 quit (Max SendQ exceeded)
07:03:13*shadowe989 joined #nim
07:03:20*shadowe989 quit (Max SendQ exceeded)
07:09:55*BlaXpirit-UA joined #nim
07:11:04*BlaXpirit quit (Ping timeout: 245 seconds)
07:12:07*BlaXpirit-UA quit (Client Quit)
07:21:19*Hakaslak quit (Quit: TODO: Generate 'Computer Sleep Quit Message')
07:21:40*Hakaslak joined #nim
07:29:51*gour joined #nim
08:06:12*z1y joined #nim
08:10:52*vendethiel quit (Ping timeout: 240 seconds)
08:14:18*BitPuffin joined #nim
08:15:25*khmm quit (Ping timeout: 272 seconds)
08:16:52*vendethiel joined #nim
08:18:52*BitPuffin quit (Ping timeout: 240 seconds)
08:19:38*khmm joined #nim
08:20:35*Hakaslak quit (Quit: TODO: Generate 'Computer Sleep Quit Message')
08:21:48*Hakaslak joined #nim
08:22:51*Hakaslak quit (Client Quit)
08:37:36*yglukhov joined #nim
08:38:30*yglukhov_ joined #nim
08:38:30*yglukhov quit (Read error: Connection reset by peer)
08:38:51*gokr_ quit (Remote host closed the connection)
08:38:55*vendethiel quit (Ping timeout: 252 seconds)
08:41:59*vendethiel joined #nim
08:51:42*khmm quit (Remote host closed the connection)
08:52:02*khmm joined #nim
08:56:38*ehaliewicz quit (Ping timeout: 258 seconds)
09:04:57*vendethiel quit (Ping timeout: 240 seconds)
09:07:37*BlaXpirit joined #nim
09:09:15*Demos quit (Ping timeout: 272 seconds)
09:10:56*z1y quit (Ping timeout: 256 seconds)
09:11:37EXetoCdyu: there's also 4f32 (4'f32)
09:14:29*vendethiel joined #nim
09:20:04*milosn joined #nim
09:29:21*Varriount_ quit (Ping timeout: 244 seconds)
09:30:13*BlaXpirit-UA joined #nim
09:30:23*BlaXpirit quit (Remote host closed the connection)
09:36:04*Varriount joined #nim
09:37:25*vendethiel quit (Ping timeout: 244 seconds)
09:40:46dyuyep
09:41:01dyurealized that after posting
09:41:18*dyu quit (Quit: Leaving)
09:48:24*vendethiel joined #nim
10:00:03*BitPuffin joined #nim
10:04:59*BitPuffin quit (Ping timeout: 272 seconds)
10:05:25*z1y joined #nim
10:12:06*BlaXpirit_UA joined #nim
10:13:12*BlaXpirit-UA quit (Ping timeout: 245 seconds)
10:30:28*matkuki joined #nim
10:33:56matkukiHi guys.
10:35:33matkukiI have a namespace macro used just for escaping indentation, so the code in a module looks grouped.
10:36:22matkukiThis is the macro: macro namespace*(head: expr, body: stmt): stmt =; result = body;
10:37:30matkukiIt works as long as there are no exportable symbols, as soon as I add an `*` to a definition, I get:
10:38:21matkuki"Error: invalid visibility: '*'". Why is that?
10:40:56*ehaliewicz joined #nim
10:45:31*ehaliewicz quit (Ping timeout: 272 seconds)
10:48:59*z1y quit (Ping timeout: 245 seconds)
10:55:38*vendethiel quit (Ping timeout: 244 seconds)
10:56:03*khmm quit (Ping timeout: 252 seconds)
10:57:15*vendethiel joined #nim
10:59:37*khmm joined #nim
11:02:29*BlaXpirit joined #nim
11:03:59*khmm quit (Ping timeout: 245 seconds)
11:04:25*EXetoC quit (Quit: WeeChat 1.0.1)
11:05:49*BlaXpirit_UA quit (Ping timeout: 258 seconds)
11:09:34*khmm joined #nim
11:21:20*Trustable joined #nim
11:36:16*milosn quit (Ping timeout: 255 seconds)
11:48:48*BitPuffin joined #nim
11:53:49*BitPuffin quit (Ping timeout: 255 seconds)
12:02:07*BlaXpirit quit (Quit: Quit Konversation)
12:02:26*BlaXpirit joined #nim
12:12:21*BitPuffin joined #nim
12:22:53matkukiFound the "immediate" pragma that fixed the issue.
12:28:47Araqmatkuki: yeah but I'd argue it's a bug anyway
12:29:07Araqplease report it
12:29:25Araqso ... next on my todo ... issue #1120
12:29:48Araqand then I think working idetools should get priority over the other "high priority" bugs
12:30:34Araqexcept for issue #871 ... *sigh*
12:35:16matkukiAraq: Will do.
12:39:05Araqthanks. btw the fix for this is trivial ;-)
12:39:24AraqI already noticed this bug but never fixed it
12:39:33Araqsee you later
12:41:26*khmm quit (Remote host closed the connection)
12:58:06*milosn joined #nim
13:00:54*milosn_ joined #nim
13:01:41*milosn quit (Client Quit)
13:01:41*milosn_ quit (Client Quit)
13:02:03*milosn joined #nim
13:14:44*z1y joined #nim
13:14:57*BlaXpirit quit (Ping timeout: 240 seconds)
13:15:13*BlaXpirit joined #nim
13:34:57*z1y quit (Ping timeout: 240 seconds)
13:39:26*nimnoob__ joined #nim
13:41:03*nimnoob__ quit (Read error: Connection reset by peer)
13:41:22*nimnoob__ joined #nim
13:42:58*bjz quit (Quit: Textual IRC Client: www.textualapp.com)
13:46:58*bjz joined #nim
13:50:18*z1y joined #nim
13:55:35*matkuki quit (Quit: ChatZilla 0.9.91.1 [Firefox 34.0.5/20141126041045])
13:58:18dom96Araq: It seems you broke something: htmlgen.hr() doesn't work anymore.
14:01:36flaviudom96: git bisect!
14:01:56dom96I ain't got no time for that.
14:05:58*EXetoC joined #nim
14:18:54Araqdom96: fixed.
14:19:03dom96cool
14:19:08Araqno need to git bisect, I know why it's broken
14:19:17Araqthe compiler is simply more strict now
14:19:39*nimnoob__ quit (Ping timeout: 265 seconds)
14:19:54Araqdom96: likely more tags in htmlgen are affected, but now you know how to fix these ;-)
14:20:11dom96yes
14:20:33dom96Weren't we going to make a better htmlgen anyway?
14:20:44Araqyup
14:21:26Araqbut that's no reason to break what is already used heavily
14:21:32dom96Also, what happens if a tag can be empty or contain children?
14:21:46Araqthen you use the empty list
14:22:00Araqpassing more args than required is allowed for immediate macros
14:22:11Araqfor better or worse...
14:22:16dom96That's fine. I think the better htmlgen module should be a nimble package anyway
14:22:55dom96Araq: Isn't varargs enough?
14:23:12Araqhrm that would be the non hacky solution
14:26:20dom96Indeed. We should adopt it :P
14:28:12*darkf quit (Quit: Leaving)
14:35:23*nimnoob__ joined #nim
14:47:31*nimnoob__ quit (Ping timeout: 255 seconds)
15:21:30*kapil__ quit (Quit: Connection closed for inactivity)
15:41:56*z1y quit (Ping timeout: 256 seconds)
15:45:51*z1y joined #nim
15:46:59*xcombelle joined #nim
15:47:18*BlaXpirit quit (Quit: Quit Konversation)
15:47:35*BlaXpirit joined #nim
15:49:51*rpag joined #nim
15:56:23*milosn quit (Ping timeout: 258 seconds)
15:56:43*z1y quit (Ping timeout: 252 seconds)
16:07:38*Jesin joined #nim
16:14:49*milosn joined #nim
16:33:51*nimnoob__ joined #nim
16:45:36*enurlyx joined #nim
16:48:11onionhammeror better yet use nim templates instead of htmlgen <_<
16:48:17enurlyxdom96: It seems the forum has a bug? I started a reply, then did preview, then someone else replied, then i preview again, then I submitted --> 404. But the forum was still running.
16:49:01*ehaliewicz joined #nim
16:49:54*Ven joined #nim
16:50:11*Ven quit (Read error: Connection reset by peer)
16:50:56*Ven joined #nim
16:51:02*Ven quit (Client Quit)
16:52:54enurlyxTo all a Merry XMas! Araq, thank you for the hard work!
16:53:28*enurlyx quit (Quit: Leaving.)
16:55:02*ehaliewicz quit (Ping timeout: 258 seconds)
16:56:44*BitPuffin quit (Ping timeout: 256 seconds)
16:56:55*Varriount|Busy quit (Ping timeout: 246 seconds)
17:02:03*nimnoob__ quit (Ping timeout: 265 seconds)
17:02:17*nimnoob__ joined #nim
17:03:35*Ven joined #nim
17:09:26*BitPuffin joined #nim
17:15:59*nimnoob__ quit (Read error: Connection reset by peer)
17:16:07*nimnoob__ joined #nim
17:16:38*gour quit (Remote host closed the connection)
17:19:31*gour joined #nim
17:28:45*nimnoob__ quit (Ping timeout: 252 seconds)
17:33:05dom96Merry christmas everyone!
17:35:26*dts|pokeball joined #nim
17:39:32onionhammerhm dom96 the nim forum is hard to browse w/ lynx
17:40:01dom96Yeah. I'm not going to fix that :P
17:40:18dts|pokeballwhats lynx?
17:43:16dom96It's a web browser, look it up.
17:43:23dts|pokeballnevar
17:55:40flaviuonionhammer: How is it hard to read?
17:56:04flaviuIt looks fine to me
17:56:19*nimnoob__ joined #nim
17:58:22*xcombelle quit (Ping timeout: 240 seconds)
18:03:34*yglukhov_ quit (Ping timeout: 245 seconds)
18:06:43*Hakaslak joined #nim
18:06:50*flaviu quit (Remote host closed the connection)
18:07:04*flaviu joined #nim
18:12:16*nimnoob__ quit (Ping timeout: 255 seconds)
18:13:44*BlaXpirit quit (Ping timeout: 250 seconds)
18:14:34*nimnoob__ joined #nim
18:15:20*BlaXpirit joined #nim
18:18:44*dts|pokeball quit (Read error: Connection reset by peer)
18:19:01*nimnoob__ quit (Ping timeout: 255 seconds)
18:19:26*dts|pokeball joined #nim
18:25:44*milosn quit (Ping timeout: 264 seconds)
18:29:20*Jesin quit (Ping timeout: 250 seconds)
18:31:05*jefus_ quit (Ping timeout: 252 seconds)
18:39:08*loz1 joined #nim
18:45:23*BlaXpirit quit (Read error: Connection reset by peer)
18:46:05*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:48:19*jefus joined #nim
18:51:09*nimnoob__ joined #nim
18:54:13*xcombelle joined #nim
18:56:19*Jesin joined #nim
19:05:45*Demos joined #nim
19:09:14*yglukhov_ joined #nim
19:16:44*nimnoob__ quit (Ping timeout: 264 seconds)
19:21:16*milosn joined #nim
19:23:30*xcombelle quit (Ping timeout: 250 seconds)
19:24:21*nimnoob__ joined #nim
19:56:23*nimnoob__ quit (Ping timeout: 244 seconds)
19:56:27*yglukhov_ quit (Quit: Be back later ...)
20:04:13*Hakaslak quit (Quit: TODO: Generate 'Computer Sleep Quit Message')
20:05:47*gour left #nim ("Leaving")
20:06:01*jasondotstar quit (Ping timeout: 272 seconds)
20:13:29*nimnoob__ joined #nim
20:23:02*nimnoob_ joined #nim
20:23:50*nimnoob__ quit (Read error: Connection reset by peer)
20:27:25Araqhi. Merry Christmas to everyone!
20:27:45gmpreussnerFrohe Weihnachten, Araq!
20:38:33dom96hey Araq
20:40:31*loz1 quit (Quit: Leaving.)
20:41:56*Demos quit (Ping timeout: 250 seconds)
20:47:37dts|pokeballAraq, as a christmas present you should write a nim to ELF compiler
20:48:17flaviuDoesn't gcc do that?
20:50:12dom96Mat is already doing that I think.
20:50:24*nimnoob_ quit (Ping timeout: 258 seconds)
20:52:02*nimnoob_ joined #nim
20:57:41*nimnoob_ quit (Ping timeout: 258 seconds)
20:57:43Araqdts|pokeball: I really consider to give you guys a Pascal backend so you can use Lazarus easily to develop UIs
20:58:00dts|pokeball:D
20:58:08dts|pokeballflaviu, yeah, but a direct one would be nice
20:58:24*yglukhov_ joined #nim
20:59:33flaviuWhy would it be nice?
20:59:51flaviuit'd just be shitty and slow
21:00:31Araqflaviu: yeah but it would improve compile times and might give us a JIT
21:00:49flaviuI'd like a working vm first, please
21:01:24dom96Writing new backends is too much effort.
21:01:29dom96for too little gain at this point
21:01:48dom96You're better off wrapping QT
21:01:59flaviuWeren't there plans to write a lua backend?
21:02:49dts|pokeball<flaviu> it'd just be shitty and slow not neccesarilly....
21:03:20flaviuYou're probably right.
21:03:52flaviuThe current VM is getting better and less buggy, no real point now
21:04:24dom96Guys, i'm writing the news post for the new release. So far I have this: https://gist.github.com/dom96/ff0dda49764da1e36e1c
21:04:30dom96Any suggestions about what I should write about?
21:04:31EXetoCflaviu: I think it was abandoned
21:04:42EXetoC2+ years ago maybe
21:04:48dom96It would be nice to have something like Rust's Road to 1.0.
21:05:18flaviu"guarantee no breaking changes"
21:05:29flaviu"no" is too strong of a word, imo
21:06:22flaviu"Take a look at some benchmarks if you don't believe us" sounds too defensive
21:08:12gmpreussner"The good news is" that is a little defensive too
21:08:19flaviuI don't like the Nim philosophy checklist approach to structuring the last two paragraphs, but may just be me.
21:09:08dom96Perhaps i'm not the best person to write this. Any volunteers?
21:09:31gmpreussnerdom96: no, i think the content is great
21:09:42gmpreussnerit just a bit of a negative touch, that's all
21:09:57gmpreussnerand punctuation is a little off as well :)
21:10:04gmpreussnercan i make some suggestions in the comments?
21:10:06dom96I don't want it to sound like a complete and utter advertisement.
21:10:17dom96sure
21:10:47gmpreussnerdom96: yeah, i understand. it doesn't need to be a marketing stunt. we'll just write up the facts without any undertone, that's all
21:10:50dom96Also I need ideas of what else to write about.
21:11:28gmpreussnerwrite that the community is growing, that cool new libraries are under development, that there is a new forum that can also be searched
21:11:51dom96Ahh yeah. The forum.
21:12:08dom96I need people who are not used to these new things to tell me about them heh.
21:17:08gmpreussnerAraq, dom96: not having _any_ breaking changes in the future is not a realistic goal
21:17:22gmpreussneri would limit it to "no breaking changes between major releases"
21:17:36gmpreussnerthat's how we handle it with our projects at work
21:17:43dom96gmpreussner: That's what I meant. Major releases being 1.x vs. 2.x
21:17:47gmpreussnerok
21:17:57dom96I should make that more explicit I suppose.
21:18:12flaviudom96: https://gist.github.com/flaviut/e0b6450c28361d377d5a
21:18:15gmpreussneryeah, im writing it up
21:18:55dom96I just updated it
21:19:00flaviuYou're not getting paid per word, keep it as concise as possible.
21:19:42dom96flaviu: That feels a bit bare.
21:20:06flaviuThat was the goal. People don't want to read an essay, the want to read and understand quickly.
21:21:52AraqI agree with flaviu
21:22:25dom96If that's the case then we may as well just put the changelog up.
21:22:59dom96People need something to read.
21:23:01flaviu`git shortlog`!
21:23:20dom96Something that they can understand otherwise they will simply close the tab too quickly.
21:23:32dom96If they see a big list of changes they will do that.
21:23:45dom96You may be only interested in them because you are invested in the project.
21:23:48dom96Others will not be.
21:24:01dom96They want to hear the generic stuff.
21:24:09dom96"These things were done to improve speed ..."
21:26:37gmpreussneri added my suggested changes in the comments: https://gist.github.com/dom96/ff0dda49764da1e36e1c
21:27:05gmpreussnerflaviu: short and concise is good, but i find yours too short.
21:27:26gmpreussnerthe release notes are useful for existing users of nim, but they must be aimed primarily at people who do not use or know nim yet
21:27:45gmpreussneras such we need to convey that the language is under VERY active development with tons of cool shit being added every release
21:28:36gmpreussnerdom96: in "look at latest benchmarks" add an actual link to the benchmarks
21:28:50*nimnoob_ joined #nim
21:31:16dom96gmpreussner: can you gist that?
21:31:25dom96Have to reformat it otherwise...
21:32:05flaviudom96: use vim?
21:32:28gmpreussnerdom96: there's not much formatting in there. just copy/paste and touch up the headline and the three highlights
21:33:08*ehaliewicz joined #nim
21:33:09dom96There is. The lines will be longer than 80 characters.
21:33:33flaviudom96: You manually trim it down to 80 chars?
21:33:39gmpreussneri would probably piggyback even more existing nim features on top of these release notes. if any significant improvements were made in any of the existing components, lets identify the most popular ones and include those in the text as well.
21:33:40flaviuIn vim, that's gq
21:34:06dom96flaviu: Yes. I don't use vim.
21:34:07flaviudom96: https://gist.github.com/flaviut/1446ccb5a1e99981de7f
21:34:28flaviuAlthough the last clause of the last sentence is a fragment
21:35:13gmpreussnerremember, at this stage of the project, release notes are not just telling that feature XYZ was changed, it must also indirectly inform unknowing users of what nim's capabilities are.
21:35:30gmpreussneronce there are a million nim users, we can focus on line item build upgrade notes
21:39:37*nimnoob_ quit (Ping timeout: 240 seconds)
21:42:38dom96What cool projects should I mention?
21:43:16*nimnoob_ joined #nim
21:43:16gmpreussneri don't know. surely there must be some?
21:43:32gmpreussnerwhen were the last release notes posted?
21:43:36gmpreussneri mean how long ago?
21:43:52dom96October 19th
21:43:57Araqask notfowl when he's around. he usually has lots of cool stuff
21:44:25Araqor take a look at what gradha is doing
21:46:45dom96Meh, let's not name any.
21:55:38flaviuWebsite breaks on iphone: https://www.modern.ie/en-us/screenshots#http%3A%2F%2Fnim-lang.org%2F
21:57:17dts|pokeballeverything breaks on iphone
21:57:20dts|pokeballcause iphone
21:58:00flaviuLets avoid flaming
21:58:03flaviuhttp://www.browserstack.com/screenshots/d0559b276ce127048fa52225c3117d066ef6777d/ios_iPhone-5S_7.0_portrait.jpg
21:58:20Araqyeah it also breaks on my smartphone
21:58:28Araqand *that* is really an issue ;-)
21:59:41dts|pokeballsorry flaviu
21:59:44flaviu.slideshow needs a clearfix
21:59:52flaviuerr, #slideshow
22:02:57*milosn quit (Ping timeout: 240 seconds)
22:04:54Araqflaviu: you have to be more specific for me
22:05:36flaviuadd `#slideshow {overflow: auto;zoom: 1;}` to the css
22:06:20flaviuBut that doesn't work, it just makes it disappear
22:06:35flaviuweird
22:08:11flaviuah, absolute position has 0px as the default hight
22:08:26flaviuwhy filwit used absolute positioning, I don't understand
22:08:43dom96I wrote a bit about Nimble.
22:10:13flaviuanyway, add don't bother with the clearfix. Just add `height: 1000px` to #slideshow
22:10:30flaviusomething something broken windows something
22:15:13*flaviu quit (Remote host closed the connection)
22:15:26*flaviu joined #nim
22:20:32*nimnoob_ quit (Ping timeout: 244 seconds)
22:23:28onionhammerwheres the nim bot announcements about commits
22:24:02Araqonionhammer: these are gone. we need nimbuild...
22:24:24*nimnoob_ joined #nim
22:24:26*flaviu quit (Remote host closed the connection)
22:29:53*Mimbus quit (Remote host closed the connection)
22:31:00*zedronar joined #nim
22:31:33Araqhi zedronar welcome
22:31:56zedronarhi Araq, thanks for the welcome
22:32:58zedronarI was trying to decide between Rust and Nim for my next hobby programming language
22:33:18zedronarseems like Nim's syntax is easier for newcomers, am I right?
22:33:46Araqthat's what most people think if you count lifetime annotations as syntax
22:36:37*bjz quit (Ping timeout: 240 seconds)
22:39:51*bjz joined #nim
22:40:52*nimnoob_ quit (Ping timeout: 240 seconds)
22:44:32*flaviu joined #nim
22:46:13zedronarwhat you mean?
22:46:32*quasinoxen quit (Ping timeout: 245 seconds)
22:48:49*quasinoxen joined #nim
22:52:03*bjz quit (Ping timeout: 244 seconds)
22:58:24*dapz joined #nim
23:02:10flaviuzedronar: He's making fun of rust, unfortunately. Please just ignore that part.
23:04:54zedronarflaviu: haha, ok
23:05:36*nimnoob_ joined #nim
23:08:37*yglukhov_ quit (Quit: Be back later ...)
23:10:32Araqno. I am not making fun of Rust at all.
23:10:51Araqon the contrary.
23:12:02Araqlifetime annotations are an inherent part of Rust and I wouldn't count them as "syntax" anymore than I count type annotations as syntax. These things surely have a syntax, but that's not where the complexity comes from.
23:12:13*nimnoob_ quit (Read error: Connection reset by peer)
23:12:36*nimnoob_ joined #nim
23:13:26*Ven joined #nim
23:13:47*dapz quit (Quit: Textual IRC Client: www.textualapp.com)
23:14:06*dapz joined #nim
23:16:44flaviuI'm not sure I understand what you're saying. Every part of the language is syntax. type annotations are syntax, lifetime annotations are syntax, if-else is syntax.
23:18:30*nimnoob_ quit (Read error: Connection reset by peer)
23:18:40dom96onionhammer: I've got a NimBuild resurrection donation jar if you wanna throw some dollars in there.
23:18:43dom96:P
23:18:53*nimnoob_ joined #nim
23:19:08Araqok, then let me put it differently: instead of asking whether Nim's syntax is easier to learn than Rust's, the better question to ask is whether Nim's type system is easier to learn than Rust's.
23:19:39dom96zedronar: I would say Nim's syntax is both easier, more expressive and more elegant than Rust's.
23:19:48dom96The semantics are also much easier to grasp.
23:20:11zedronardom96: Awesome. I'm annoyed by Rust complexity.
23:20:25Araqand even this is misleading since a "type system" is not everything.
23:21:43zedronarAraq: Simplify it even more. If a beginner tells you that he only wants to learn Rust or Nim. Which one would you recommend and why?
23:22:25Araqthat is the question that you ask the inventor of Nim?
23:23:59*quasinoxen quit (Read error: Connection reset by peer)
23:24:35gmpreussnerdoes nim have an elevator pitch yet? :)
23:24:37zedronarAraq: Good point.
23:25:20*quasinoxen joined #nim
23:25:40gmpreussnerzedronar: i looked at Rust as the savior of my existence, but i gave up on it. i was going to give up programming altogether and become farmer, but then i stumbled upon nim :)
23:26:29gmpreussnerRust is probably more stable at this point (they have some serious dollars behind their project), but just by looking at the documentation you can already tell that nim is going to be totally awesome.
23:26:47*dts|pokeball quit (Read error: Connection reset by peer)
23:27:28zedronargmpreussner: Great. I'll give it a try then.
23:28:29*dts|pokeball joined #nim
23:35:23*z1y joined #nim
23:47:30*nimnoob_ quit (Ping timeout: 258 seconds)
23:50:09*zedronar quit (Quit: Page closed)
23:50:42*nimnoob_ joined #nim
23:51:07*Ven quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
23:56:38*nimnoob_ quit (Ping timeout: 244 seconds)