<< 20-02-2018 >>

00:01:22FromGitter<Varriount> enthus1ast: Considering that Windows GUI looks to be back when 100GB was a standard hard drive...
00:02:30FromGitter<Varriount> I don't think it's the indexing service. My guess would be either Antivirus or a Shell extension.
00:12:46enthus1astonly Lite5h4dow could give us clarity :)
00:14:18*sz0 quit (Quit: Connection closed for inactivity)
00:40:37*cyuz89yfd9 joined #nim
00:50:17*gangstacat joined #nim
01:26:15*athenot joined #nim
01:32:43*athenot quit (Remote host closed the connection)
02:23:14*SenasOzys quit (Ping timeout: 255 seconds)
02:27:16*yglukhov joined #nim
02:31:27*yglukhov quit (Ping timeout: 248 seconds)
02:53:20*Snircle quit (Quit: Textual IRC Client: www.textualapp.com)
02:54:08*chemist69 quit (Ping timeout: 255 seconds)
02:58:09*vlad1777d quit (Ping timeout: 260 seconds)
03:08:12*chemist69 joined #nim
03:10:28*endragor joined #nim
03:11:13*endragor quit (Remote host closed the connection)
03:11:17*xkapastel quit (Quit: Connection closed for inactivity)
03:11:39*endragor joined #nim
03:51:49*Snircle joined #nim
04:29:01*r3d9u11 joined #nim
04:31:45*arecacea1 quit (Remote host closed the connection)
04:32:08*arecacea1 joined #nim
05:00:22*Snircle quit (Quit: Textual IRC Client: www.textualapp.com)
05:02:23*arthurz quit (Ping timeout: 248 seconds)
05:05:50*arthurz joined #nim
05:07:45*MyMind joined #nim
05:09:21*Sembei quit (Ping timeout: 248 seconds)
05:15:28*r3d9u11 quit (Remote host closed the connection)
05:31:14*endragor quit (Remote host closed the connection)
06:04:34*endragor joined #nim
06:08:21*r3d9u11 joined #nim
06:33:37*nsf joined #nim
06:42:21*Pisuke joined #nim
06:44:14*MyMind quit (Ping timeout: 276 seconds)
06:53:15*solitudesf joined #nim
07:01:11*Senketsu quit (Ping timeout: 268 seconds)
07:12:42*Senketsu joined #nim
07:17:05*vlad1777d joined #nim
07:24:52*endragor quit (Remote host closed the connection)
07:39:44*endragor joined #nim
07:43:52*xet7 quit (Ping timeout: 260 seconds)
07:57:28*gokr joined #nim
07:57:38*ofelas quit (Quit: shutdown -h now)
07:58:18*xet7 joined #nim
07:58:21*rokups joined #nim
08:00:51*solitudesf quit (Ping timeout: 256 seconds)
08:35:21*PMunch joined #nim
08:55:59*enthus1ast quit (Ping timeout: 248 seconds)
09:02:31*floppydh joined #nim
09:02:44*enthus1ast joined #nim
09:09:52*SenasOzys joined #nim
09:20:47*Yardanico_ joined #nim
09:25:36*Yardanico_ quit (Read error: Connection reset by peer)
09:32:32*gokr quit (Ping timeout: 256 seconds)
09:32:36*Vladar joined #nim
09:32:59*Arrrr joined #nim
09:32:59*Arrrr quit (Changing host)
09:32:59*Arrrr joined #nim
09:37:31*coffeepot joined #nim
10:57:03*j_rod_s quit (Read error: Connection reset by peer)
11:00:10*endragor quit (Read error: Connection reset by peer)
11:01:51FromGitter<tim-st> Is this hard to change in nimsuggest: https://gist.github.com/anonymous/003e8481e57f258bd156e8527402faf5 ?
11:02:43FromGitter<tim-st> especially when the source code is bigger this is a bit annoying
11:03:49Araqlooks reasonably easy to change
11:04:05FromGitter<tim-st> thanks, I will make issue than
11:04:15Araqin semProcAux overwrite the forwarded line information
11:04:41FromGitter<tim-st> will have a look, I hope I understand it^^
11:18:00FromGitter<tim-st> It's too hard to understand for me. I will create an issue for now just to have it
11:18:47Araqok
11:23:55dom96miran: yes
11:24:11dom96the latter enables inheritance
11:28:49*vlad1777d quit (Ping timeout: 256 seconds)
11:38:26*couven92 joined #nim
11:44:40FromGitter<mratsim> I’m really wondering on how can function call syntax triggers an error but Nim happily compiles if using th emethod call syntax: https://github.com/nim-lang/Nim/issues/7238
11:46:02Araqsounds like the dot syntax shouldn't compile either
11:47:07Araqif it compiles, does it produce the correct results and C code?
11:48:58FromGitter<mratsim> yes
11:49:17*endragor joined #nim
11:50:28FromGitter<mratsim> well I tried with “256” to check if it properly changed. Trying with uint32/uint16 as soon as i update my devel version
11:52:33FromGitter<mratsim> In the C code it properly gets the size ⏎ ⏎ ```code paste, see link``` [https://gitter.im/nim-lang/Nim?at=5a8c0c007685a046389bc76e]
11:56:16Araqok then, then sizeof's sem'checking seems to be wrong
12:04:35*SenasOzys quit (Ping timeout: 276 seconds)
12:07:47*niv quit (Quit: Ping timeout (120 seconds))
12:12:47*niv joined #nim
12:15:32*niv quit (Client Quit)
12:15:57*niv joined #nim
12:16:13*SenasOzys joined #nim
12:30:48*niv quit (Ping timeout: 240 seconds)
12:40:25*arthurz quit (Ping timeout: 252 seconds)
12:40:26Yardanico@zacharycarter did you see that? https://github.com/blog/2503-deprecation-notice-removing-anonymous-gist-creation
12:41:49YardanicoI don't know what alternative is the best for the playground, but we need to think about it
12:41:58*niv joined #nim
12:43:31Arrrr"In addition, many people already have a combination of tools authenticated with GitHub that allow them to create gists they own."
12:45:16YardanicoYeah, probably best solution is just to add GitHub authentication
12:46:49*Snircle joined #nim
12:49:12Arrrror pastebin
12:49:50Arrrror maybe store them in whatever place the playground is hosted and remove them as they grow old
12:51:14Yardanicowell I think self-hosting is not easy to do
12:51:17Yardanicobecause people can abuse that
12:55:57*floppydh quit (Quit: WeeChat 2.0.1)
12:57:13*floppydh joined #nim
13:01:42*arthurz joined #nim
13:03:05enthus1astthe playground could also be used as a little nim tutorial
13:06:23PMunchYeah, someone suggested writing something like the golang tour: https://tour.golang.org/welcome/1
13:06:28enthus1astyeah
13:06:38enthus1astjust wanted to paste the same link :)
13:07:01PMunchWhich would be pretty easy considering you can just POST stuff to play and you will get the results back :)
13:07:33enthus1astbut i think the go tour is a little clunky to use
13:10:07PMunchOh?
13:10:24enthus1astfor example you don't see where you are exactly in the whole documentation etc, something like a "readthedocs" / "playground" crossover would be awesome
13:10:45enthus1astwith a offline docu download link etc.
13:12:04*sendell joined #nim
13:12:32PMunchOoh, yeah that's interesting
13:16:27enthus1astand some other idea, one thing that made php(sic) so popular was the ability to post comments on the documentation
13:17:12enthus1astso you always found solutions, user provided example code etc etc (sometimes copy paste ready) in the comments
13:20:37PMunchInline in the uploaded documentation?
13:21:47enthus1asthttp://php.net/manual/en/function.mysql-real-escape-string.php
13:24:28enthus1astso like "combine the docs with the forum" thing
13:25:38PMunchAh, like a section at the bottom
13:26:04PMunchYeah that might be helpful
13:27:12enthus1astit would (maybe) attract more users and let the community share their nice examples unbureaucratically
13:29:58livcdsure but it's a chicken egg problem. You need the ecosystem and you need the people to build the ecosystem.
13:33:08*gokr joined #nim
13:37:13*xkapastel joined #nim
13:41:09*endragor quit (Ping timeout: 264 seconds)
13:44:35*r3d9u11 quit (Remote host closed the connection)
13:45:36*r3d9u11 joined #nim
13:51:42*endragor joined #nim
13:55:51*endragor_ joined #nim
13:57:08*Arrrr quit (Read error: Connection reset by peer)
13:59:09*endragor quit (Ping timeout: 264 seconds)
13:59:26*endragor_ quit (Remote host closed the connection)
14:00:04*endragor joined #nim
14:16:57*SenasOzys quit (Remote host closed the connection)
14:18:34*SenasOzys joined #nim
14:21:15dom96enthus1ast: workaround is to request 'https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts'
14:21:20dom96Still trying to figure out the issue though
14:24:21*endragor quit (Remote host closed the connection)
14:24:57*endragor joined #nim
14:29:30*yglukhov joined #nim
14:34:01dom96huh, I could have sworn I reproduced it on 'devel'
14:34:14dom96but now I can only reproduce it on this PR https://github.com/nim-lang/Nim/pull/7149
14:42:32*r3d9u11 quit (Quit: Leaving)
14:48:55FromGitter<Vindaar> Clojure does something similar like php in their docs. It's pretty sweet, e.g.: https://clojuredocs.org/clojure.core/map
14:51:44PMunchOh yeah, the examples section of Clojure is really nice
14:51:52PMunchMakes it so much easier to learn
14:52:02FromGitter<Vindaar> indeed
14:52:17*endragor quit (Ping timeout: 248 seconds)
14:54:27*kunev quit (Ping timeout: 240 seconds)
14:54:59*solitudesf joined #nim
14:57:21*kunev joined #nim
14:58:26*yglukhov quit (Remote host closed the connection)
14:59:03*yglukhov joined #nim
15:03:29*yglukhov quit (Ping timeout: 248 seconds)
15:04:12*yglukhov joined #nim
15:06:06FromGitter<zetashift> woaw the clojure doc is excellent
15:10:19PMunchYup
15:10:30PMunchPretty much the only resource you need to learn Clojure :)
15:10:51*UxerUospr joined #nim
15:11:08FromGitter<zetashift> I'm still browsing; I think this beats Elixir's hexdocs
15:11:21PMunchThe idea of having examples right next to the definition is really nice as you are then able to figure out exactly how to use any function
15:11:46PMunchAnd the examples also note any common gotchas and such
15:13:04*BitPuffin joined #nim
15:15:42FromGitter<zetashift> But is it a good time now to update the Nim docs/add docs seeing how v0.18 and more more breaking changes are coming
15:16:10PMunchIt's always a good time for better docs :)
15:17:45*gokr quit (Ping timeout: 256 seconds)
15:26:02*yay joined #nim
15:37:43*yglukhov quit (Remote host closed the connection)
15:38:10*yay quit (Quit: Page closed)
15:50:45FromGitter<tim-st> I noticed some days ago that sometimes when I compile my file and have an assertion error and recompile the very same file the line number is on the first run decremented by one, and on all later fails the same. Did someone noticed this before too?
15:50:50*dddddd joined #nim
15:53:01FromGitter<zetashift> very true PMunch!
15:58:11*j_rod_s joined #nim
16:03:23*endragor joined #nim
16:04:40*arthurz quit ()
16:04:53*endragor quit (Remote host closed the connection)
16:14:04*endragor joined #nim
16:16:55*gokr joined #nim
16:17:01*gokr left #nim (#nim)
16:19:40FromGitter<Varriount> @tim-st Could you post the code?
16:22:44*SenasOzys_ joined #nim
16:23:02*SenasOzys quit (Ping timeout: 260 seconds)
16:24:31FromGitter<tim-st> No, I dont face this problem atm, but I traced two different procs in both situation I'm sure this happened (next time I will try to build an example code). Maybe the line number is cached somewhere or similar. The first time this appeared, the line number was `while true:`and of course there is no error, than I recompiled and it told me line number +1 which was actually the mistake
16:26:27*PMunch quit (Quit: Leaving)
16:28:49FromGitter<Varriount> @tim-st What operating system and C compiler are you using?
16:30:49FromGitter<tim-st> windows 10 with nim devel and gcc version from nim site (maybe the first time it happened I was at windows 7, nim 0.17.2, same gcc); I will generate an example next time; I'm still working at the same code, I'm sure it happens again
16:31:16FromGitter<tim-st> gcc (x86_64-win32-seh-rev1, Built by MinGW-W64 project) 6.3.0
16:32:28*endragor quit (Remote host closed the connection)
16:32:53*floppydh quit (Quit: WeeChat 2.0.1)
16:32:59FromGitter<Varriount> I just wonder if it's not a misbehaving antivirus or shell extension that's preventing your source code from being properly saved
16:34:13FromGitter<tim-st> no, I don't think so, I execute it using vscode nim plugin
16:34:46FromGitter<Varriount> The files in nimcache don't usually contain line numbers. Even when they do, the compiler doesn't use them.
16:35:18FromGitter<tim-st> I think it happened in recursive called procs only, will definetly have a deeper look into it next time it happens
16:45:29*Trustable joined #nim
16:50:07*SenasOzys_ quit (Ping timeout: 248 seconds)
17:06:54*couven92 quit (Quit: Client disconnecting)
17:17:50*FromGitter quit (Ping timeout: 255 seconds)
17:18:02*FromGitter joined #nim
17:38:18*yglukhov joined #nim
17:42:32*yglukhov quit (Ping timeout: 252 seconds)
17:52:44*SenasOzys_ joined #nim
17:59:45*gokr joined #nim
17:59:49*gokr left #nim (#nim)
18:00:17*themagician joined #nim
18:01:16*miran_ joined #nim
18:11:23*sendell quit (Remote host closed the connection)
18:19:54*icebattle joined #nim
18:40:01*miran_ quit (Remote host closed the connection)
18:41:38*miran_ joined #nim
18:44:30*miran_ quit (Remote host closed the connection)
19:01:30*PMunch joined #nim
19:16:23*coffeepot quit (Remote host closed the connection)
19:20:22*Elronnd quit (Remote host closed the connection)
19:23:42*BitPuffin quit (Remote host closed the connection)
19:38:46*Vladar quit (Quit: Leaving)
19:44:14*elronnd joined #nim
19:47:08*elronnd is now known as Elronnd
20:06:57PMunchHmm, strange bug with rfind
20:07:19PMunchSearching "TEST = a;" for "a;" yields -1
20:10:27PMunchHmm, doing it in a separate file works fine
20:15:15PMunchHmm "a;" != "a;"
20:15:17PMunchThat's odd
20:16:08PMunchHuh, "a;".len == 6
20:19:28dom96!eval echo("a;".len)
20:19:30NimBot2
20:19:39dom96You sure? :)
20:19:57PMunchHaha, that's obviously not the code I'm running
20:20:32PMunchecho "\"" & node.input & "\"" => "a;"
20:20:38PMunchecho node.input.len => 6
20:20:54dom96Use .repr
20:21:00PMunchfor i in node.input: 61, 3B, 00, 00, 00, 00
20:21:24PMunch0x7ff3f8ce0c88"a;\0\0\0\0"
20:21:25PMunchrepr
20:27:19FromGitter<nitely> I've been bitten by null terminated string more than once by now too
20:29:24FromGitter<nitely> but I guess it makes interop with C easier, maybe? Although, that has never been a problem in other langs for me
20:33:38*yglukhov joined #nim
20:33:50PMunchBut how can a string like "TEST = a;", which only goes through Nim code doing slices end up being "a;\0\0\0\0"?
20:33:55PMunchThis is pure Nim code
20:37:02FromGitter<nitely> you have an off-by-one bug? copying the null char?
20:37:15PMunchHmm, choosenim update "#head" didn't help either
20:37:46PMunchAha
20:37:51*yglukhov quit (Ping timeout: 248 seconds)
20:38:10PMunchA slice like input[pos .. input.len] copies the null byte..
20:38:18FromGitter<nitely> yep
20:38:37PMunchWell that's confusing
20:39:18FromGitter<nitely> I think that's a feature, sadly
20:39:42PMunchYeah i know
20:40:47FromGitter<Vindaar> Isn't that simply because the slice is including the upper index, i.e. you'd want to use input.high instead?
20:41:04PMunchYup
20:57:25dom96I don't think .high helps much here
20:57:46*rokups quit (Quit: Connection closed for inactivity)
21:04:16*jxy quit (Quit: leaving)
21:05:06PMunchIt did
21:05:55PMunchProblem was that I was slicing with [pos .. input.len], changing it to input.high stopped it from including the null-character
21:07:03*jxy joined #nim
21:10:26dom96But you've got multiple null characters in there, no?
21:10:43dom96the convention btw is: [pos..<input.len]
21:10:47PMunchYeah, it was run multiple times
21:11:03PMunchEach cut adding a new null
21:12:21*MJCaley joined #nim
21:13:14dom96I see
21:20:46FromGitter<Vindaar> Ah, on my way home I finally realized what I found confusing about the string slice. The length of the datatype underlying the string is really len + 1, so that a slice to len is still in bounds, whereas for a seq it would be out of bounds. Ok, that does make it a special case in a way :-)
21:22:00PMunchYup
21:22:20PMunchMaybe there should be a special syntax for getting the entire null terminated string?
21:22:41PMunchI've run into this thing once or twice..
21:24:12*ipjk joined #nim
21:27:43dom96I think this deserves a bug report :)
21:28:00dom96It might be worth not to be consistent here and raise an error
21:31:03*ipjk quit (Quit: Leaving)
21:31:10*UxerUospr quit (Quit: Lost terminal)
21:33:08PMunchWell it is technically correct, so it's not really a bug
21:33:26PMunchBut I agree that this should perhaps be treated as a special case
21:33:34PMunchOh well, I'm off to bed
21:33:35*PMunch quit (Quit: leaving)
21:39:53*Trustable quit (Remote host closed the connection)
21:44:56*yglukhov joined #nim
21:45:36*nsf quit (Quit: WeeChat 2.0.1)
21:49:42*yglukhov quit (Ping timeout: 265 seconds)
22:19:14*solitudesf quit (Ping timeout: 256 seconds)
22:30:14*MJCaley quit (Quit: MJCaley)
22:50:57*gangstacat quit (Ping timeout: 260 seconds)
22:52:55*gangstacat joined #nim
22:57:51*DaleK5whr joined #nim
22:58:05*DaleK5whr left #nim (#nim)
23:04:10*rockcavera quit (Read error: Connection reset by peer)
23:04:29*rockcavera joined #nim
23:06:40*miran quit (Ping timeout: 260 seconds)
23:07:29*cyuz89yfd9 quit (Quit: WeeChat 2.0.1)
23:13:26*far4ia4650 joined #nim
23:19:38*instrud joined #nim
23:27:55*themagician quit ()
23:38:54*vlad1777d joined #nim
23:48:38FromGitter<honewatson> Is there a nim code formatter like the go formatter?