<< 25-07-2018 >>
00:12:42FromGitter<gogolxdong> copy. There is still a lot to learn , Nim is profound.
00:15:45*arecacea1 quit (Remote host closed the connection)
00:16:04*arecacea1 joined #nim
00:16:30*Jesin quit (Quit: Leaving)
00:18:58shashlickAraq: Google also uses trunk based development
00:18:59shashlickhttps://m-cacm.acm.org/magazines/2016/7/204032-why-google-stores-billions-of-lines-of-code-in-a-single-repository/fulltext
00:26:43*dddddd quit (Remote host closed the connection)
00:37:03*stefanos82 quit (Quit: Quitting for now...)
00:39:55*craigger quit (Quit: bye)
00:42:33*craigger joined #nim
01:02:54*leorize quit (Ping timeout: 256 seconds)
01:10:34*mwbrown quit (Ping timeout: 264 seconds)
01:11:35*mwbrown joined #nim
01:26:19FromGitter<gogolxdong> @Varriount thanks for your snippet to demonstrate peg usage , will learn more about how to use peg, currently use `let reg = re"(CreateEnumType\(|CreateDataType\(|CreateManagedType\()+.*"` works well.
01:29:43*leorize joined #nim
01:40:52*Shivelight joined #nim
01:50:39*yglukhov[i] joined #nim
01:51:08*endragor joined #nim
01:54:35*yglukhov[i] quit (Ping timeout: 240 seconds)
01:55:36*endragor quit (Ping timeout: 256 seconds)
02:05:30*NimBot joined #nim
02:18:32*ieatnerds joined #nim
02:38:32*TheKing[m] quit (Ping timeout: 256 seconds)
02:41:22*Shivelight quit (Ping timeout: 256 seconds)
02:41:22*hitchhooker[m] quit (Ping timeout: 256 seconds)
02:41:40*Shivelight joined #nim
02:41:42*hitchhooker[m] joined #nim
02:42:25*TheKing[m] joined #nim
02:52:23FromGitter<Quelklef> ... Does a `try ... finally ...` catch all errors??
02:52:45FromGitter<Quelklef> It seems to be catching or suppressing an IndexError for me
02:53:11FromGitter<Quelklef> Nope, wth
02:55:00FromGitter<Quelklef> oh it's because `-d:release` duh
03:00:43*ieatnerds quit (Ping timeout: 268 seconds)
03:16:55*Jesin joined #nim
03:35:25shashlickanyone gotten spacemacs to work with nim-mode?
03:37:10FromGitter<kaushalmodi> shashlick: I don't use spacemacs, but there shouldn't be much involved to get nim-mode to work.
03:37:19FromGitter<kaushalmodi> You just install and require it
03:38:12FromGitter<kaushalmodi> Here's all nim setup that I do: https://github.com/kaushalmodi/.emacs.d/blob/master/setup-files/setup-nim.el
03:38:29shashlickonce I install it and open a nim file, it loads fine but it hangs
03:39:15FromGitter<kaushalmodi> nimsuggest is probably the culprit
03:39:23FromGitter<kaushalmodi> what happens if you don't enable nimsuggest-mode?
03:40:05shashlickwill have to figure out how to disable it
03:41:10FromGitter<kaushalmodi> Don't add `nimsuggest-mode` to `nim-mode-hook` and also set `nim-nimsuggest-path` to nil or "" (haven't tried that)
03:41:31shashlickwell, nimsuggest does load up in processes so its able to find it
03:43:55FromGitter<kaushalmodi> You can set nimsuggest-path to nil: https://github.com/nim-lang/nim-mode/blob/35f4b2cb2d4c142f6f7f0e3ffb06c87b81bb8c26/nim-vars.el#L137
03:45:11FromGitter<kaushalmodi> ```(use-package nim-mode ⏎ :preface ⏎ (setq nimsuggest-path nil) ⏎ :defer t))``` ⏎ ⏎ Writing out of memory, but something like this should work [https://gitter.im/nim-lang/Nim?at=5b57f247db4bcb16e875e767]
03:45:35shashlickwell, so this is spacemacs with a different way of doing everything
03:45:50shashlickthought I'd try it out again but there has to be some issue or the other
03:45:58FromGitter<kaushalmodi> I've heard you can dump in use-package forms or any regular elisp in private layers
03:47:21FromGitter<kaushalmodi> I did a light research on config in spacemacs to support one of the users of my ox-hugo package. This is what worked: https://ox-hugo.scripter.co/doc/usage/
03:50:00*endragor joined #nim
03:50:32*Shivelight quit (Quit: Connection closed for inactivity)
04:03:20*NamPNQ joined #nim
04:18:54shashlick@kaushalmodi: so I've restarted from scratch, no spacemacs, pure emacs, installed evil, nim-mode and company
04:18:59shashlickhow do I get completion to work?
04:22:39FromGitter<kaushalmodi> Look at company-mode
04:23:05FromGitter<kaushalmodi> Well, just read that you mentioned that already
04:23:50FromGitter<kaushalmodi> I don't use fancy completion, just `hippie-expand` (inbuilt)
04:25:45FromGitter<kaushalmodi> company-mode when enabled in any prog-mode should do the right thing (but I haven't used it)
04:26:43shashlickokay, I guess i'm feeling too lazy to bumble through Emacs setup for nim right now
04:27:13*nsf joined #nim
04:31:26FromGitter<kaushalmodi> Yeah, Emacs is not one of those editors that you configure for good in a day. It'll stick only if you realize its true power and use it.
04:34:04shashlicki'm that way with vim, but would be nice to have suggestions
04:34:19shashlickreally liked vscode but don't want to use up all my RAM
04:44:03ftsf@dom96, trying to give Jester a try via nimble, requires nim>=0.18.1 which doesn't appear to have been released yet, should I be using an older version of jester instead?
04:44:41FromGitter<rayman22201> use Nim devel. It's stable
04:45:59FromGitter<rayman22201> devel is 0.18.1 btw
04:47:04ftsfok
04:47:42FromGitter<Quelklef> "stable"
04:47:47FromGitter<Quelklef> depends on what features you're using
04:47:53FromGitter<Quelklef> stay away from Static[T] ;-)
04:47:59FromGitter<Quelklef> otherwise you'll be ok
04:48:54ftsfi'm deving on windows unfortunately so getting a devel build might be a challenge, but i'll give it a try
04:48:57FromGitter<rayman22201> lol, sorry @Quelklef I know you are having bad troubles with generics right now :-0
04:49:04ftsfi miss linux =(
04:49:14FromGitter<Quelklef> haha
04:49:30FromGitter<Quelklef> to be fair, the thing I was trying to do with it was an optimization that'd remove, like, 0.0001% of runtime
04:49:43FromGitter<Quelklef> but *also* it'd make the code feel cleaner (to me) which I wanted
04:49:57FromGitter<Quelklef> I submitted a bug report, so hopefully it'll be fixed ;)
04:50:00FromGitter<Quelklef> :)*
04:50:16FromGitter<rayman22201> also, it's just a good idea to test the type system in weird ways. That's how we get a better compiler :-)
04:50:36FromGitter<Quelklef> true that
04:50:46FromGitter<Quelklef> Whenever I'm submitting a lot of bugs I feel like I'm being bad
04:50:52FromGitter<Quelklef> But then I'm like, wait, no, that's dumb
04:53:47FromGitter<rayman22201> Definitely not bad! creativity is never bad!
04:54:14FromGitter<Quelklef> How about abuse?
04:54:27FromGitter<Quelklef> I'm talkin' term-rewriting macros that change semantics, baby (not actually)
04:55:12FromGitter<rayman22201> it's called "Creative Quality Assurance" :-P
04:55:22FromGitter<rayman22201> @ftsf I think choosenim works on windows?
04:55:32FromGitter<rayman22201> though I haven't tried it recently
04:55:39ftsf@rayman22201 i tried that, but it's detected as a virus >_<
04:56:25FromGitter<rayman22201> get a better virus software :-P
04:57:00ftsfit's the inbuilt windows one
04:57:45ftsfmaybe I can override it somehow
04:57:48FromGitter<rayman22201> I am trying it now, and I am not having any issues with virus detection
04:58:12FromGitter<rayman22201> I downloaded the zip release, and used `runme.bat` with powershell
04:58:43FromGitter<rayman22201> It's doing the fresh install of 0.18.0. I will try develop when it finishes
04:58:47*Shivelight joined #nim
04:58:52ftsfmmm i found a way to override it
04:58:54ftsfyay
04:59:02FromGitter<rayman22201> cool beans!
04:59:14ftsfexcept it's using mingw32, hopefully that won't be an issue
04:59:27ftsf(instead of 64)
05:04:48ftsfhmm "choosenim.exe devel" fails on trying to show a progress bar =(
05:07:44FromGitter<rayman22201> that is less helpful than what I get... which is a failure because I need to upgrade OpenSSL
05:08:04FromGitter<rayman22201> try this: ` .\.nimble\bin\choosenim.exe "#head"`
05:08:19FromGitter<rayman22201> the # needs to be quotes
05:09:08FromGitter<rayman22201> good news is, ⏎ ⏎ ```code paste, see link``` [https://gitter.im/nim-lang/Nim?at=5b5805f432d98c2ed2b264f1]
05:09:19FromGitter<rayman22201> it is the 64-bit version of mingw
05:10:03ftsfyeah, same fails on progress bar
05:14:35FromGitter<rayman22201> hrmmm. what version of windows are you using, and are you use cmd or powershell?
05:18:47ftsfwindows 10, git bash
05:19:02ftsfmaybe that's why
05:19:41*xylef joined #nim
05:19:52FromGitter<rayman22201> yeah, git bash is based on cygwin isn't it? that could cause issues
05:20:11FromGitter<rayman22201> Nim works really well in WSL, if you want to go that route
05:21:06ftsfmmm it's all very confusing =)
05:21:26ftsfmaybe I should just give up on windows
05:21:47ftsfthat said, i just managed to manually build nim \o/
05:23:04*leorize quit (Ping timeout: 260 seconds)
05:24:56FromGitter<rayman22201> lol. I just did the same
05:25:04FromGitter<rayman22201> the manual build process on windows seems to work fine
05:26:08ftsfyay now i can get back to trying jester
05:26:21ftsfthanks!
05:26:49FromGitter<rayman22201> 👍
05:28:05*floppydh quit (Remote host closed the connection)
05:28:06FromGitter<rayman22201> *thinks to myself* not sure if I should report this as a bug on choosenim
05:29:13*floppydh joined #nim
05:31:10FromGitter<rayman22201> actually! @ftsf, something to note, I just remembered. The newest version of Jester is built on httpbeast, which is linux only. If you use it on windows it falls back to a slower http server. (I don't remember all the details.)
05:32:46ftsfcheers, i'm devving on windows, but gonna deploy to linux
05:33:03ftsf(why aren't I building on linux, derp)
05:33:19ftsfyay cross compiling fun
05:37:53FromGitter<rayman22201> cool. You are probably making life harder on yourself lol, but it's good to test the cross-compiling workflow :-)
06:00:05*Vladar joined #nim
06:02:49*leorize joined #nim
06:05:01ftsfdefinitely, i should just switch back to linux =)
06:05:12*yglukhov[i] joined #nim
06:05:20ftsfunfortunately I'm using Unity for some work stuff and the linux version is pretty unreliable
06:06:04*NamPNQ quit (Remote host closed the connection)
06:09:47FromGitter<Quelklef> Is there any shorthand for `nim c -r X; rm X`?
06:09:49FromGitter<Quelklef> built-in?
06:10:00FromGitter<Quelklef> I hate having my workspace cluttered with binary files
06:15:35Araqshashlick: I know
06:15:46*yglukhov[i] quit (Remote host closed the connection)
06:23:43*Sembei joined #nim
06:26:04*Pisuke quit (Ping timeout: 268 seconds)
06:34:57FromGitter<gogolxdong> How to assign in tuple or something like this ⏎ ⏎ ```(vmodlName,wsdlName,version,value) = (n[1].strVal, n[2].strVal,n[3].strVal, n[4])``` [https://gitter.im/nim-lang/Nim?at=5b581a11db4bcb16e8763f7e]
06:56:07*jjido joined #nim
06:57:13*ieatnerds joined #nim
07:02:02*ieatnerds quit (Ping timeout: 256 seconds)
07:07:31*yglukhov[i] joined #nim
07:24:20ftsfhmm nimPNG broken in devel =(
07:26:11ftsfseems to be caused by using ' in {foo, bar}' instead of ' in [foo, bar]'
07:29:12Araqftsf: it's a regression, I will fix it tonight
07:29:18ftsfhurrah!
07:30:31*Shivelight quit (Quit: Connection closed for inactivity)
07:31:09ftsfalso noticed filestream.write(foo.uint8) is trying to coerce it to a string rather than write the data now
07:40:05*NimBot joined #nim
08:15:11*amosbird quit (Quit: ZNC 1.7.0 - https://znc.in)
08:15:27*amosbird joined #nim
08:16:17*dddddd joined #nim
08:23:57*yglukhov[i] quit (Ping timeout: 240 seconds)
08:26:56*jjido quit (Ping timeout: 268 seconds)
08:44:38*ng0 joined #nim
08:52:28FromGitter<dom96> Ftsf: you can use jester 0.2.1 if you don't want to upgrade your Nim
08:53:27*yglukhov[i] joined #nim
08:59:04*ng0 quit (Quit: Alexa, when is the end of world?)
08:59:29*ng0 joined #nim
09:10:14*dddddd quit (Ping timeout: 256 seconds)
09:45:43*yglukhov[i] quit (Read error: Connection reset by peer)
09:46:17*yglukhov[i] joined #nim
10:27:19*abm joined #nim
10:34:36FromGitter<Yardanico> (https://files.gitter.im/nim-lang/Nim/TNx8/Screenshot_2.png)
10:34:38FromGitter<Yardanico> @dom96 new github dashboard (in beta, you can opt in)
10:35:03FromGitter<Yardanico> they finally changed it so it takes all space
10:39:11*dddddd joined #nim
10:40:54dom96Looks nice
10:48:34*leorize quit (Ping timeout: 260 seconds)
11:20:20FromGitter<kaushalmodi> @Quelklef You can use the `--out` option to specify the output directory.
11:22:42FromGitter<Quelklef> `nim c --out /dev/nill -r X`?
11:22:48FromGitter<Quelklef> :thinking:
11:22:58FromGitter<Quelklef> but thank you!
11:23:12FromGitter<Quelklef> `/dev/null`*
11:24:28*ieatnerds joined #nim
11:24:30*yglukhov[i] quit (Read error: Connection reset by peer)
11:24:51*yglukhov[i] joined #nim
11:27:33FromGitter<Quelklef> What's the algorithm for a `seq[i]`?
11:27:41FromGitter<Quelklef> that is, indexing into a seq?
11:28:04FromGitter<Quelklef> Does it start from 0 and increment or do something clever like start from the last index and search from there or anything
11:29:57*yglukhov_ joined #nim
11:31:04*dddddd quit (Quit: Hasta otra..)
11:31:12*yglukhov[i] quit (Ping timeout: 256 seconds)
11:31:23*dddddd joined #nim
11:32:19FromGitter<kaushalmodi> shashlick: About suggestions for emacs, I am a very small data point for auto-completion, etc. suggestions as I can suggest only what I am using. But I'd ask you to ping the #emacs IRC for better suggestions as you'll get a more collective response on various options. Also search/ask on r/emacs subreddit and the official Emacs help mailing list. Folks are really responsive on all those channels.
11:35:17*yglukhov_ quit (Ping timeout: 260 seconds)
11:37:13*yglukhov[i] joined #nim
11:49:52*xylef quit (Quit: WeeChat 2.2)
11:52:35*ieatnerds quit (Ping timeout: 276 seconds)
11:55:15*ieatnerds joined #nim
11:58:47*yglukhov_ joined #nim
11:59:29*yglukhov[i] quit (Ping timeout: 248 seconds)
11:59:53*yglukhov[i] joined #nim
12:03:06*yglukhov_ quit (Ping timeout: 244 seconds)
12:09:26*yglukhov[i] quit (Read error: Connection reset by peer)
12:10:24*yglukhov_ joined #nim
12:10:37*livcd quit (Changing host)
12:10:37*livcd joined #nim
12:23:04*ieatnerds quit (Ping timeout: 260 seconds)
12:36:02*leorize joined #nim
12:41:12*endragor quit (Remote host closed the connection)
12:47:11*MyMind joined #nim
12:47:49*yglukhov[i] joined #nim
12:48:33*Sembei quit (Ping timeout: 248 seconds)
12:50:45*yglukhov_ quit (Ping timeout: 264 seconds)
12:56:40*endragor joined #nim
12:56:56FromGitter<citycide> my understanding is that `{.closure.}` procs are fairly expensive, but is that mitigated at all if they're also `{.inline.}` and used only once or twice?
12:57:29FromGitter<mratsim> you can’t inline a closure, it’s an object
12:58:25FromGitter<mratsim> you should instead use a closure more to offset the cost of its creation
13:00:58*endragor quit (Ping timeout: 244 seconds)
13:01:09*ieatnerds joined #nim
13:01:43FromGitter<citycide> @mratsim got it, thanks. I'm trying to reduce some code duplication but it's in an iterator that's kind of becoming monstrous. would also like to break it up but there's lots of parameters/state involved
13:02:19*stefanos82 joined #nim
13:04:26*yglukhov_ joined #nim
13:06:16*yglukhov[i] quit (Read error: Connection reset by peer)
13:06:48*yglukhov[i] joined #nim
13:08:56*yglukho__ joined #nim
13:08:57*yglukhov[i] quit (Read error: Connection reset by peer)
13:09:38*yglukhov_ quit (Read error: Connection reset by peer)
13:11:31*yglukhov[i] joined #nim
13:12:31*krux02 joined #nim
13:12:43Calinouhttps://github.com/tldr-pages/tldr/pull/2218 has been merged :)
13:12:46Calinouboth nim and nimble are now in tldr
13:14:13dom96yay
13:14:21krux02Araq: https://github.com/krux02/Nim/blob/fix-alloc-type-signature/tests/system/talloc.nim
13:15:01*yglukhov_ joined #nim
13:15:12krux02The reason you closed the PR that I made was that in that file I used to many cast operations. I just did that because that was the original way the test was written and all allocations were assigned to the same pointer.
13:15:32*yglukho__ quit (Ping timeout: 268 seconds)
13:15:49krux02but because I changed the type signature the way I did, I could get rid of ever type casting that has been done in the file.
13:16:42*yglukho__ joined #nim
13:16:42*yglukhov_ quit (Read error: Connection reset by peer)
13:18:08*yglukhov[i] quit (Read error: Connection reset by peer)
13:21:25FromGitter<kaushalmodi> Calinou: Awesome! I have just this one comment: https://github.com/tldr-pages/tldr/pull/2207#pullrequestreview-140306868
13:22:09*yglukho__ quit (Ping timeout: 265 seconds)
13:22:41*yglukhov[i] joined #nim
13:24:09Calinouyeah, but according to the tldr style guide, full option names should be preferred
13:24:19Calinouhttps://github.com/tldr-pages/tldr/blob/master/contributing-guides/style-guide.md
13:24:59Calinouand https://github.com/tldr-pages/tldr/blob/master/CONTRIBUTING.md
13:25:05Calinou"Try to incorporate the spelled-out version of single-letter options in the example's description. The goal is to allow people to understand the syntax of the commands, not just memorize it."
13:28:45FromGitter<kaushalmodi> Calinou: where do they say that? Sorry, on phone, searched for long, full, found none.
13:28:56Calinouin CONTRIBUTING.md :)
13:29:24FromGitter<kaushalmodi> One of their own examples actually uses -f instead of --render.
13:31:53FromGitter<kaushalmodi> They also have ln -s in an example instead of ln --symbolic
13:34:24FromGitter<kaushalmodi> > Try to incorporate the spelled-out version of single-letter options in the example's description.
13:34:33FromGitter<kaushalmodi> Thanks, found the above.
13:34:47Calinouyeah, though they do make exceptions for common options
13:34:55Calinouthey do say *options* and not subcommands :P
13:35:47FromGitter<kaushalmodi> But it's a grey area. I believe almost all would be using `nim c` all the time. It's as ubiquitous as `ln -s` (i.e. no one uses --symbolic, not even tldr :))
13:38:16*ieatnerds quit (Ping timeout: 256 seconds)
13:44:16dom96yeah, I agree about the 'c'
13:46:36krux02I would add the option --debugger:native, too.
13:48:08krux02Compile a source file with debug information: `nim compile --debugger:native {{file.nim}}`
13:54:27*nsf quit (Quit: WeeChat 2.1)
13:55:47*yglukhov_ joined #nim
13:59:09*yglukhov[i] quit (Ping timeout: 264 seconds)
14:01:42*yglukhov[i] joined #nim
14:05:13*yglukho__ joined #nim
14:05:29*yglukhov_ quit (Ping timeout: 268 seconds)
14:08:04*yglukhov[i] quit (Ping timeout: 260 seconds)
14:11:10*yglukhov[i] joined #nim
14:11:14*yglukho__ quit (Ping timeout: 244 seconds)
14:12:35*yglukhov_ joined #nim
14:12:35*yglukhov[i] quit (Read error: Connection reset by peer)
14:17:15*yglukhov[i] joined #nim
14:19:35*yglukhov_ quit (Ping timeout: 240 seconds)
14:24:31*yglukhov_ joined #nim
14:27:27*yglukhov[i] quit (Ping timeout: 240 seconds)
14:47:32*yglukhov_ quit (Read error: Connection reset by peer)
14:48:04*yglukhov[i] joined #nim
14:52:34*drazan quit (Remote host closed the connection)
14:54:27*drazan joined #nim
14:57:36*dddddd quit (Remote host closed the connection)
15:11:18*xylef joined #nim
15:12:56shashlickkrux02: did you have any luck getting auto-complete and suggestions to work with emacs + nim-mode
15:23:27krux02shashlick, it worked for some time, yes
15:24:02krux02but I disabled it, because nimsuggest froze too often for my personal tast and freezing emacs with it.
15:25:41krux02shashlick, this is my nim mode init script http://ix.io/1ilP
15:26:03krux02as you can see, I disable everything in nim
15:27:42krux02shashlick, here I think this is everything in my config http://ix.io/1ilQ
15:28:05*stefanos82 quit (Ping timeout: 240 seconds)
15:28:16krux02no guarantee that anything works
15:29:25shashlickkrux02: thanks - I tried spacemacs but it just hangs so gave up on that, pure emacs, no suggestions or autocomplete works
15:29:54krux02sometimes on pure emacs it also just hangs
15:30:00krux02that's why i disabled so much
15:30:14Araqkrux02: I don't care about this create stuff, sorry
15:30:43Araqthis should have been project specific or in a separate module at least
15:31:06Araqpointless aliases.
15:31:08krux02Araq what do you mean project specific?
15:31:35Araqthey never should have been added to system.nim
15:31:47krux02well that is true
15:31:54krux02maybe in a memory.nim
15:32:25Araqor in lowlevelsugar.nim
15:32:30krux02I generally like the idea that there is manual memory allocation
15:33:07Araqsure but that's called alloc/realloc/dealloc in Nim.
15:33:48krux02so you would like the have only the ``pointer`` version in system.nim?
15:34:44krux02s/the have/to have/
15:35:09Araqor a typedesc version, proc alloc[T](what: typedesc[T]): T = cast[T](alloc sizeof(T))
15:35:54Araqor rather proc alloc[T](what: typedesc[T]): ptr T = cast[ptr T](alloc sizeof(T))
15:36:08krux02but isn't that exactly what create does?
15:36:32Araqyeah but 'create' is not in our style guidelines
15:37:16krux02well, wasn't it that manually managed stuff is initialized with createXXX?
15:37:45krux02I think that is the idea behind this.
15:37:49Araqdunno but I simply don't like it
15:38:21Araq'create' implies a high level action, not an alias for the first step of a creation
15:38:49krux02that is true.
15:39:45krux02I could rename them all to just be called alloc
15:39:52krux02and allocShared
15:41:23*stefanos82 joined #nim
15:42:32krux02so then there would only these families be left ``alloc, alloc0, allocShared, allowShared0``
15:42:48krux02but here I don't like that the non initialized version is shorter.
15:43:03krux02yes it is faster, but it is not the recommended version.
15:43:46krux02normally you want 0 memory, unless you know that you write to every field before you read from it.
15:45:12*erratic quit (Ping timeout: 256 seconds)
15:55:28*ieatnerds joined #nim
16:05:51*xylef quit (Quit: WeeChat 2.2)
16:06:22*krux02 quit (Remote host closed the connection)
16:06:47*xylef joined #nim
16:10:48*Trustable joined #nim
16:31:13FromGitter<Yardanico> what's the best way to throw a compile-time error?
16:31:18FromGitter<Yardanico> from my code :)
16:33:18*yglukhov_ joined #nim
16:33:18*yglukhov[i] quit (Read error: Connection reset by peer)
16:33:25FromGitter<Quelklef> `static: assert X`
16:35:47FromGitter<Yardanico> @Quelklef thank you!
16:49:20*ftsf quit (Ping timeout: 244 seconds)
16:55:22FromGitter<Quelklef> Yup
16:55:32FromGitter<Quelklef> anytime
16:56:15*floppydh quit (Quit: WeeChat 2.1)
16:56:57*yglukhov_ quit (Read error: Connection reset by peer)
16:57:50*xylef quit (Quit: WeeChat 2.2)
17:03:26*xylef joined #nim
17:09:18*yglukhov[i] joined #nim
17:13:35*yglukhov[i] quit (Ping timeout: 240 seconds)
17:14:30*yglukhov[i] joined #nim
17:22:07*yglukhov[i] quit (Read error: Connection reset by peer)
17:22:39*yglukhov[i] joined #nim
17:23:52shashlickso no one here uses emacs/spacemacs with nim, with suggestions and autocomplete working?
17:25:30*xylef quit (Quit: WeeChat 2.2)
17:33:10*yglukhov[i] quit (Remote host closed the connection)
17:33:46*yglukhov[i] joined #nim
17:37:57*yglukhov[i] quit (Ping timeout: 240 seconds)
17:50:35*Ven`` joined #nim
17:52:18dom96I don't even use VS Code with suggestions/autocomplete
17:52:44dom96it just doesn't work at all anymore
17:55:34*Ven`` quit (Ping timeout: 260 seconds)
17:56:44stefanos82dom96: I can see from Aporia that it has an autocomplete.vim that depends on nimsuggest
17:57:10stefanos82in case you know, is nimsuggest the same as gocode semantically speaking?
17:57:19dom96no idea
17:57:32dom96Aporia's autocomplete.nim targets an older nimsuggest too
17:57:39stefanos82ah I see
17:57:39*Ven`` joined #nim
17:58:51stefanos82in case autocomplete could be used as a background process, it could be easy enough to use it with a variety of editors / IDEs
17:59:16Araqit is a background process
18:01:37*dorelix_ quit (Ping timeout: 248 seconds)
18:08:17shashlickso basically no functioning suggestions/autocomplete in any editor at this point? then i'd just continue working with vim
18:09:19AraqI'm sure nimsuggest would work for me (TM)
18:09:27AraqI'm on the wrong machine to test it though
18:14:04*Ven`` quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
18:17:10*dorelix joined #nim
18:18:00*Ven`` joined #nim
18:19:40shashlickwell it's one thing for nimsuggest to work and another to have an editor which can use it correctly
18:21:09shashlicknvim-nim hasn't been updated in a year
18:21:23shashlickand zah's plugin doesn't support nimsuggest
18:21:33shashlicknow if even vscode isn't working then why bother movign
18:22:27*Ven`` quit (Ping timeout: 240 seconds)
18:32:25*arecacea1 quit (Remote host closed the connection)
18:32:44*arecacea1 joined #nim
18:34:10*Chainsawdomist joined #nim
18:35:19dom96md5 not available in JS D:
18:36:07ChainsawdomistAnybody feel like handholding me with a problem lol
18:36:26dom96Chainsawdomist: sure, ask away
18:36:33FromGitter<kayabaNerve> dom96: You mean a Nim lib's md5 impl doesn't work in JS?
18:36:39dom96yep
18:36:45FromGitter<kayabaNerve> Which Nim lib?
18:36:49dom96stdlib
18:37:14FromGitter<kayabaNerve> Ah
18:38:01ChainsawdomistIt isn't specific to Nim, but I'm having trouble using Nake. Getting a "command not found" after installing it with Nimble on Windows and Mac. Should I be registering "nake" as a command somewhere? I'm sort of new to programming and that sort of thing
18:38:30FromGitter<kayabaNerve> Why is MD5 and SHA1 in the stdlib?
18:39:01FromGitter<kayabaNerve> Why not include a wider set of options that are still secure or just none at all so people are enticed to go to better places like nimcrypto?
18:39:07dom96Chainsawdomist: add ~/.nimble/bin to your PATH
18:39:58FromGitter<kayabaNerve> https://shattered.io ⏎ https://en.wikipedia.org/wiki/MD5#Collision_vulnerabilities ⏎ ⏎ Reference ^^ [https://gitter.im/nim-lang/Nim?at=5b58c3fe07be4357bdecfe9b]
18:40:44dom96kayabaNerve: md5 is commonly used, and the use cases often don't require security
18:41:50FromGitter<kayabaNerve> It is; it shouldn't be; I'm pretty sure 99% do, just not critically
18:42:09FromGitter<kayabaNerve> There's two modern uses. ⏎ 1) Verifying the file is what it says it is. ⏎ 2) Verifying the integrity of the file.
18:43:12FromGitter<kayabaNerve> Most downloads offer a hash to verify the file integrity. When hash collisions exist, you can upload a fake file, and claim it's the original.
18:44:20FromGitter<kayabaNerve> That's for security. You can also say it's to distinct against other files, but not to verify that file is that file versus different from other files (did I get the v1.0 or v1.1 download?). In that case, it's not for security, however I don't think most people use it like that and that's the 1%.
18:44:46ChainsawdomistThat did the trick @dom96 . Thanks!
18:45:02FromGitter<kayabaNerve> And it's not critical to verify integrity but that's like allowing a Google login where you can make a typo on any letter of the password. It shouldn't be done.
19:14:38*Chainsawdomist quit (Quit: Page closed)
19:19:30*dddddd joined #nim
19:25:43*Ven`` joined #nim
19:31:59*Altarrel joined #nim
19:35:16*Ven`` quit (Ping timeout: 256 seconds)
19:40:17*Vladar quit (Quit: Leaving)
19:45:03*Jesin quit (Quit: Leaving)
19:54:00*yglukhov[i] joined #nim
19:54:34*ieatnerds quit (Quit: leaving)
20:01:30*icebattl1 joined #nim
20:01:44*icebattle quit (Quit: leaving)
20:01:49*icebattl1 quit (Client Quit)
20:02:11*icebattle joined #nim
20:05:06*icebattle quit (Client Quit)
20:05:40*icebattle joined #nim
20:11:09*drazan quit (Ping timeout: 264 seconds)
20:13:09*Altarrel left #nim (#nim)
20:20:53*nsf joined #nim
20:25:08*drazan joined #nim
20:36:37*erratic joined #nim
20:36:57*icebattle quit (Ping timeout: 240 seconds)
20:37:14*icebattle joined #nim
20:37:36*literal quit (Read error: Connection reset by peer)
20:39:00*literal joined #nim
20:45:39*Trustable quit (Remote host closed the connection)
20:59:23*nekits quit (Remote host closed the connection)
20:59:49*nekits joined #nim
21:03:28*yglukhov[i] quit (Remote host closed the connection)
21:14:45*nsf quit (Quit: WeeChat 2.1)
21:39:57*Altarrel joined #nim
21:50:42AltarrelI'm having trouble using c2nim on https://github.com/discordapp/discord-rpc. I have no C/C++ experience or knowledge and I have read through the Nim documentation and written a bit of code. Overally my experience in this area is minimal. I tried running c2nim on https://github.com/discordapp/discord-rpc/blob/master/include/discord_rpc.h but I get discord_rpc.h(76, 39) Error: token expected: ;
22:13:11*Pisuke joined #nim
22:16:04*MyMind quit (Ping timeout: 256 seconds)
22:20:37*Altarrel quit (Quit: Page closed)
22:32:25*tiorock joined #nim
22:32:26*tiorock quit (Changing host)
22:32:26*tiorock joined #nim
22:32:26*rockcavera is now known as Guest10129
22:32:26*Guest10129 quit (Killed (weber.freenode.net (Nickname regained by services)))
22:32:26*tiorock is now known as rockcavera
22:41:58FromGitter<rayman22201> try using https://github.com/genotrance/nimgen
22:45:59*CcxWrk quit (Quit: ZNC 1.6.5 - http://znc.in)
22:46:40*CcxWrk joined #nim
23:00:24*icebattle quit (Ping timeout: 256 seconds)
23:05:34*ng0 quit (Quit: Alexa, when is the end of world?)
23:06:01*Cthalupa quit (Ping timeout: 265 seconds)
23:07:03*Cthalupa joined #nim
23:25:05*rayman22201 joined #nim
23:49:57*ftsf joined #nim
23:54:40*ftsf quit (Client Quit)