<<13-09-2019>>

00:00:20*laaron quit (Quit: ZNC 1.7.1 - https://znc.in)
00:00:53FromGitter<mratsim> oh right @brentp
00:01:00*laaron joined #nim
00:01:32*fov60 joined #nim
00:01:47FromGitter<mratsim> otherwise @erhlee-bird if you preffer working on a blank slate, wrapping Nvidia rapids would be nice: https://rapids.ai/
00:02:38fov60any body here familiar with basic sdl+opengl on windows and mac
00:03:11FromGitter<erhlee-bird> @mratsim, I really like the research you've been doing in Arraymancer and laser. So I'm pretty keen on trying to get something out of Arraymancer
00:03:20FromGitter<mratsim> cool :)
00:03:22FromGitter<erhlee-bird> I switched to head and the nanosecond issue is fixed with nvcc
00:03:41FromGitter<erhlee-bird> That was a head-scratcher. I'm glad you had already dealt with it :)
00:08:12*ng0 quit (Ping timeout: 260 seconds)
00:08:40*laaron quit (Ping timeout: 260 seconds)
00:09:46*Hideki_ joined #nim
00:09:47*laaron joined #nim
00:11:43*nif quit (Quit: ...)
00:11:52*nif joined #nim
00:14:03*Hideki_ quit (Ping timeout: 245 seconds)
00:17:43FromGitter<mratsim> that was a mindboggling one
00:19:10shashlick@mratsim which repo, rapids has a bunch
00:20:16*ng0 joined #nim
00:30:03FromGitter<deech> Is there a compile time reflection proc that shows me what `distinct` types a given type can be coerced to? For instance, I'd like: ⏎ ⏎ ```type ⏎ MyInt = distinct int ⏎ static: ⏎ echo coerceable(10)``` ⏎ ⏎ to output `[int, MyInt]`. [https://gitter.im/nim-lang/Nim?at=5d7ae30b5d40aa0d7d27e45c]
00:35:24*gangstacat quit (Quit: Ĝis!)
00:37:47*fov60 quit (Ping timeout: 276 seconds)
00:38:16*gangstacat joined #nim
00:39:30*abm quit (Quit: Leaving)
00:40:58*ng0 quit (Quit: Alexa, when is the end of world?)
00:56:53*fjellfras joined #nim
01:05:30*btop quit (Ping timeout: 265 seconds)
01:20:22FromGitter<mratsim> @shaslick, most important is CuDF
01:20:54FromGitter<mratsim> It should be the base for all other repos I think since it introduces the base datastructure
01:21:19FromGitter<mratsim> @deech distinctBase
01:31:02*wildtrees quit (Quit: Leaving)
01:33:47*theelous3 joined #nim
01:38:32*btop joined #nim
01:39:23*theelous3 quit (Remote host closed the connection)
01:39:47*theelous3 joined #nim
01:40:26*fov60 joined #nim
01:43:38*btop quit (Ping timeout: 246 seconds)
01:43:52*owl_000 joined #nim
02:02:37fov60what is libdl and does nim link it by default
02:03:27fov60lol nvm
02:03:32fov60im dumb
02:03:39fov60gotta sleep
02:03:44*fov60 left #nim ("WeeChat 2.5")
02:35:32*nif quit (Quit: ...)
02:35:42*nif joined #nim
02:46:58*btop joined #nim
02:50:10*Hideki_ joined #nim
02:52:02*btop quit (Ping timeout: 240 seconds)
02:54:56*Hideki_ quit (Ping timeout: 276 seconds)
02:58:50*theelous3 quit (Ping timeout: 276 seconds)
03:18:34*laaron quit (Remote host closed the connection)
03:21:27*laaron joined #nim
03:27:56*chemist69 quit (Ping timeout: 246 seconds)
03:30:07*chemist69 joined #nim
03:49:45*absolutejam1 joined #nim
03:54:32*absolutejam1 quit (Ping timeout: 246 seconds)
04:04:53*dddddd quit (Remote host closed the connection)
04:10:49*btop joined #nim
04:27:47*rockcavera quit (Remote host closed the connection)
04:33:25*nsf joined #nim
04:36:16*actuallybatman joined #nim
05:02:20*owl_000 quit (Ping timeout: 265 seconds)
05:08:16*narimiran joined #nim
05:44:51*Hideki_ joined #nim
05:48:40*solitudesf joined #nim
05:55:51*sealmove quit (Quit: WeeChat 2.6)
05:59:47*absolutejam1 joined #nim
06:03:14*laaron quit (Quit: ZNC 1.7.1 - https://znc.in)
06:03:35*laaron joined #nim
06:24:29*Hideki_ quit (Remote host closed the connection)
06:25:15*Hideki_ joined #nim
06:29:27Araqdeech: there is macros.baseType or similar
06:30:05*Hideki_ quit (Ping timeout: 276 seconds)
06:42:52*btop quit (Ping timeout: 265 seconds)
06:44:30Araqhttps://stackoverflow.com/questions/13366083/why-does-the-arrow-operator-in-c-exist/13366168#13366168
06:53:59*absolutejam1 quit (Ping timeout: 265 seconds)
06:58:47*Hideki_ joined #nim
06:59:46*krux02 joined #nim
07:00:00*gmpreussner quit (Quit: kthxbye)
07:04:34*gmpreussner joined #nim
07:04:36*owl_000 joined #nim
07:09:14*Hideki_ quit (Ping timeout: 240 seconds)
07:13:16*btop joined #nim
07:18:50*btop quit (Ping timeout: 276 seconds)
07:19:35FromGitter<zacharycarter> I'm resurrecting frag - basically just starting a new engine project with the same name focusing on 3d
07:20:03FromGitter<zacharycarter> which is just going to be a cleaned up and refactored verison of what I've been working on for the past few months
07:20:40*laaron quit (Remote host closed the connection)
07:21:45*Hideki_ joined #nim
07:22:41*laaron joined #nim
07:28:40*absolutejam1 joined #nim
07:42:59*floppydh joined #nim
07:43:27Araqcool
08:01:46*Hideki_ quit (Remote host closed the connection)
08:04:26*Hideki_ joined #nim
08:08:38*Hideki_ quit (Ping timeout: 246 seconds)
08:09:43*PMunch joined #nim
08:14:19FromGitter<zacharycarter> going to have deferred and forward rendering, ssao, shadowmaps etc
08:14:37FromGitter<zacharycarter> using bgfx for the graphics api
08:15:25FromGitter<zacharycarter> and hopefully expose a much cleaner / nicer API than frag had
08:18:37*couven92 joined #nim
08:18:48*ng0 joined #nim
08:26:01FromGitter<YiyuanGH> I find a typo in Nim Tutorial (Part I), Operator section: there is an extra close parenthsis at the end of first paragraph.
08:28:33*Hideki_ joined #nim
08:31:50FromGitter<YiyuanGH> When I learned the Parameters section of Tutorial I, I got confused about the parameter shadowing example. I wonder whether it is different from var paremeter and whether it has some practical use.
08:34:32*actuallybatman quit (Ping timeout: 246 seconds)
08:41:31*Vladar joined #nim
08:46:21*actuallybatman joined #nim
08:51:02Hideki_My PR of Nim codegen (beta) for OpenAPI was merged. I hope Nim folks will improve the generator. (https://github.com/OpenAPITools/openapi-generator/pull/3879)
08:54:09Hideki_Sample generated codes are in https://github.com/OpenAPITools/openapi-generator/tree/master/samples/client/petstore/nim
08:54:40narimiran@YiyuanGH i'm looking at that section and i don't see the typo you mention. but im probably not looking good enough — you can send a PR with the fix
09:03:35PMunchYiyuanGH, narimiran, that paranthesis belongs to the one that starts at "(Postfix operators are not", looks right to me
09:04:26*Hideki_ quit (Remote host closed the connection)
09:05:00narimiransame here
09:05:08*Hideki_ joined #nim
09:09:28*Hideki_ quit (Ping timeout: 245 seconds)
09:14:20*Hideki_ joined #nim
09:23:47*btop joined #nim
09:28:38*btop quit (Ping timeout: 245 seconds)
09:37:32*actuallybatman quit (Ping timeout: 246 seconds)
09:41:48FromGitter<YiyuanGH> @PMunch Thanks. I was too careless.
09:44:33*Hideki_ quit (Remote host closed the connection)
09:50:46*Hideki_ joined #nim
10:01:37FromGitter<alehander42> Araq, i kinda agree that
10:01:41FromGitter<alehander42> seeing pointer chasing
10:01:45*Vladar quit (Remote host closed the connection)
10:01:58FromGitter<alehander42> with `->` is nice
10:02:22FromGitter<alehander42> but this is all about explicit vs implicit
10:03:30FromGitter<alehander42> agree with one of the comments on the stack overflow link*
10:03:56*Hideki_ quit (Remote host closed the connection)
10:13:22*Hideki_ joined #nim
10:17:38*Hideki_ quit (Ping timeout: 240 seconds)
10:40:46*laaron quit (Remote host closed the connection)
10:43:20*laaron joined #nim
10:43:39*dddddd joined #nim
10:55:16*Hideki_ joined #nim
11:00:50*absolutejam1 quit (Ping timeout: 246 seconds)
11:02:51*laaron quit (Remote host closed the connection)
11:05:29*laaron joined #nim
11:09:00euantorNim got a mention in the most recent sourcehut blog :) https://sourcehut.org/blog/2019-09-12-sourcehut-makes-bsd-software-better/
11:11:52*btop joined #nim
11:17:23*btop quit (Ping timeout: 276 seconds)
11:18:55*Hideki_ quit (Remote host closed the connection)
11:19:50*Hideki_ joined #nim
11:24:32*Hideki_ quit (Ping timeout: 276 seconds)
11:32:50*absolutejam1 joined #nim
11:38:59*absolutejam1 quit (Ping timeout: 246 seconds)
11:47:47*absolutejam1 joined #nim
11:52:41*absolutejam1 quit (Ping timeout: 265 seconds)
11:55:01*Hideki_ joined #nim
12:00:02*xet7 quit (Quit: Leaving)
12:00:18*xet7 joined #nim
12:02:05*Hideki_ quit (Ping timeout: 246 seconds)
12:06:15*nsf quit (Quit: WeeChat 2.5)
12:20:44*Vladar joined #nim
12:24:14*rockcavera joined #nim
12:25:17*Hideki_ joined #nim
12:27:49leorizeZevv, narimiran, disruptek: how's the refactored nim.nvim been?
12:27:59narimiranno problem here
12:28:22leorizeI'm probably gonna start adding features soon, so I'd like to know if everyone consider it ready for merging to `master`
12:30:12*absolutejam1 joined #nim
12:34:07*fjellfras quit (Quit: Leaving)
12:37:01shashlick@narimiran looks like you are looking at compile crash issues, please try out tissue
12:37:15narimiranshashlick: i'm doing that with the help of tissue :)
12:37:59shashlickOh neat!
12:38:32shashlickLet me know if any feedback or features needed
12:42:40*Hideki_ quit (Remote host closed the connection)
12:44:05*absolutejam1 quit (Ping timeout: 246 seconds)
12:48:39Zevvleorize: fine I guess, but I didnt update very recently
12:48:57*absolutejam1 joined #nim
12:48:59ZevvI have a request though. I want to kill nimsuggest with a keystroke :)
12:50:19*pbb quit (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.)
12:50:40*pbb joined #nim
12:51:57narimiranZevv: doable, map a key to `call nim#suggest#ProjectStopAll()`
12:53:38Zevvof course its doable :)
12:59:15narimiranshashlick: the most important thing i would like to see changed is — how people write their bug reports! goddammit, show me the buggy behaviour, without commented out problem or without the need for manually turn on some custom switches
12:59:53*btop joined #nim
13:00:11narimiranneither tissue can properly work on such examples, neither do i see the problem when i try to quickly copy-paste it when trying to reproduce it
13:02:05narimiranand yeah, it is a big problem when you have 1200+ open issues. no time to carefully go through each and every one of them, to see if there's something hiding in the code
13:04:50*btop quit (Ping timeout: 240 seconds)
13:05:52shashlickMakes sense
13:08:06narimiranok, rant over. one thing that we might want to implement (and highlight in our issue template) for tissue is: if the bug report needs a non-default command (default is `nim c -r`), please specify it in the comment on the first line of the code, e.g. `nim c --threads:on` or `nim js`
13:09:05shashlickAgreed - tissue does infer the flags but you need those key words
13:09:18shashlickHappy to hear it still works
13:09:34shashlickAre you using it to post back comments or create tests?
13:09:51shashlickOr on interactive mode?
13:11:08narimirani'm just running it locally to see where tissue reports "NOCRASH", to see if: (1) it has indeed has been fixed, (2) there is still some problem, (3) one of the above mentioned situations where you need to enable some flag or uncomment something, etc.
13:11:57shashlickOk cool - I figure it should also help with fixing bugs
13:12:13shashlickSince you can have it run the test case in a loop
13:12:33shashlickAnd can fix compiler in parallel
13:12:48shashlickIt can also run nim_temp
13:12:49narimiranthat's too advanced for me, i'm a simple man :)
13:13:35leorizeZevv: call nim#suggest#ProjectStop() instead if you only want to stop the current one
13:14:29shashlickIt's a feature for lazy people :) I know I used it a lot when fixing simple issues
13:15:44shashlickAnyway, happy to hear it is helping - let me know if you need any specific features for your workflow
13:16:14Araqshashlick, I tinkered with --gc:boehm and IMO it should be the goto solution for your case, "I have shared memory in DLLs"
13:16:28Araqso I wonder why it crashed for you
13:18:15shashlickIt used to work in 0.19.6 but not in 0.20.x
13:18:42shashlickI need to do a bisect and figure out the break
13:18:54shashlickBut will take a long time
13:19:21shashlickLots of commits in that release
13:19:24Araqoh I fixed a regression, devel might be fine
13:20:09shashlickAah, I'll try it out
13:23:53*PMunch quit (Read error: Connection reset by peer)
13:27:19*cgfuh joined #nim
14:12:36*btop joined #nim
14:25:18*couven92 quit (Ping timeout: 245 seconds)
14:32:59*Trustable joined #nim
14:35:02*btop quit (Ping timeout: 246 seconds)
14:41:04*Trustable quit (Remote host closed the connection)
14:44:10*floppydh quit (Quit: WeeChat 2.6)
14:47:07*krux02 quit (Remote host closed the connection)
14:50:00*jken quit (Disconnected by services)
14:50:50*jken_ joined #nim
14:52:02*laaron quit (Quit: ZNC 1.7.1 - https://znc.in)
14:53:44*laaron joined #nim
14:55:52*absolutejam1 quit (Ping timeout: 265 seconds)
15:02:34*absolutejam1 joined #nim
15:06:56*btop joined #nim
15:08:24*ng0 quit (Ping timeout: 260 seconds)
15:08:27FromGitter<awr1> @zacharycarter cool stuff!
15:09:17FromGitter<zacharycarter> @awr1 yeah - I'm excited :D
15:09:28FromGitter<zacharycarter> hope to get an initial release out by the end of the month
15:09:49FromGitter<awr1> the renderer i'm currently working will be using be using some kind of Forward+/tiled forward render strategy
15:09:49FromGitter<zacharycarter> also I want to add android support - I have a (what I think is) neat idea for an AR app
15:10:08FromGitter<zacharycarter> ah cool
15:10:20FromGitter<awr1> in terms of android support, i saw this thing on the forum a while ago
15:10:51FromGitter<awr1> a prototypical APK compilation and signing utility
15:10:52*ng0 joined #nim
15:10:55FromGitter<zacharycarter> well I had android support working in the initial version of frag
15:11:00FromGitter<zacharycarter> it was pita using the NDK
15:11:17FromGitter<awr1> that didn't require the android build tools
15:11:48FromGitter<zacharycarter> ah cool
15:12:15FromGitter<awr1> https://forum.nim-lang.org/t/4840#
15:12:53FromGitter<zacharycarter> thanks for sharing - this will be good to reference :)
15:13:07*couven92 joined #nim
15:14:42FromGitter<awr1> np
15:15:12*absolutejam1 quit (Ping timeout: 265 seconds)
15:15:22FromGitter<zacharycarter> since I've gotten back into warhammer I thought it'd be cool if I made an AR app for looking at a 40k battle
15:16:07FromGitter<awr1> sounds interesting!
15:16:17FromGitter<awr1> somehow i have had yet to try AR/VR
15:17:28FromGitter<zacharycarter> I don't know how I'll determine that a model should die in the AR app
15:17:38FromGitter<zacharycarter> but details
15:19:07*pbb quit (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.)
15:19:24*pbb joined #nim
15:21:23FromGitter<zacharycarter> I haven't done anything yet with either, either :P
15:21:28FromGitter<zacharycarter> but I'm more interested in AR than VR
15:22:42federico3 -offtopic :)
15:24:16Araqcool offtopic topics remain in #nim :P
15:27:16*nsf joined #nim
15:27:21FromGitter<awr1> i halfway wonder if I should do these XCB bindings the "proper" way where i parse the XML schema they have
15:27:41FromGitter<awr1> or just bind to the stuff i need
15:27:47FromGitter<awr1> alternatively: nimterop
15:28:15narimiranfederico3: you usually post even ontopic links in the #offtopic, and now *this* has made you post here? :D :D
15:28:42*nif quit (Quit: ...)
15:28:53*nif joined #nim
15:28:53FromGitter<awr1> i assume nim-offtopic has no gitter bridge
15:29:03FromGitter<awr1> am too lazy to download an IRC client
15:29:08narimiranit is nim-twitch, or something like that
15:30:57leorizenim-lang/twitch
15:31:10leorizeoriginally was used as a bridge to Araq's stream I believe
15:31:47FromGitter<awr1> o ok
15:32:07FromGitter<alehander42> https://gitter.im/nim-lang/twitch
15:42:40*Vladar quit (Remote host closed the connection)
15:46:58*couven92 quit (Ping timeout: 245 seconds)
15:55:15*Manigold joined #nim
15:55:20Manigoldrockcavera
15:55:21Manigoldeae
16:01:08*ng0 quit (Ping timeout: 260 seconds)
16:02:24*Manigold quit ()
16:02:31*ng0 joined #nim
16:12:16shashlick@awr1 - will you compile xcb from source or use the installed bindings?
16:12:31shashlicklibraries in /usr/lib i man
16:13:14FromGitter<awr1> right now i'm just binding against xcb/xcb.h
16:14:55*nif quit (Quit: ...)
16:15:06*nif_ joined #nim
16:27:33*crem quit (Ping timeout: 258 seconds)
16:35:47*actuallybatman joined #nim
16:37:49*abm joined #nim
16:42:27*NotCreative joined #nim
17:03:45*sealmove joined #nim
17:05:08*gangstacat quit (Ping timeout: 276 seconds)
17:07:41*nsf quit (Quit: WeeChat 2.5)
17:12:47sealmoveIf I have a variable of type T, how do I create a variable of type ref T?
17:13:51Araqsealmove, usually you start with 'ref T' then
17:13:59Araqbut this also works
17:14:11Araqvar y: ref T; new(y); y[] = x
17:15:05*absolutejam1 joined #nim
17:16:23sealmoveerm, my code is a little more involved :S https://pastebin.com/DMcNzzNB
17:19:44sealmoveresult shouldn't be a reference, but I want to create a reference to result
17:19:46*gangstacat joined #nim
17:20:40sealmovemaybe proc new[T](a: var ref T) can help?
17:21:09sealmovehmm no
17:21:41shashlick@awr1 - here's a wrapper for xcb that works on linux for the standard library install - http://ix.io/1V0i/nim
17:21:52shashlick`nim c -d:xcbStd xcb.nim`
17:21:59*laaron quit (Remote host closed the connection)
17:22:03shashlickif you want to static bind, just add `-d:xcbStatic`
17:22:13shashlickyou need the v020 branch of nimterop though
17:28:13*absolutejam1 quit (Ping timeout: 245 seconds)
17:28:38*laaron joined #nim
17:31:42sealmoveError: type mismatch: got <ref DefaultBigEndian> but expected 'DefaultBigEndian = ref DefaultBigEndian:ObjectType'
17:31:48sealmove:S
17:32:57sealmovewhat does `ref T:ObjectType` mean?
17:40:53*btop quit (Ping timeout: 276 seconds)
17:41:31sealmoveok I figured it out
17:42:32*btop joined #nim
17:51:18*wildtrees joined #nim
17:51:45*rockcavera quit (Remote host closed the connection)
17:52:34*wildtrees quit (Remote host closed the connection)
17:53:01*wildtrees joined #nim
18:03:10*sealmove quit (Quit: WeeChat 2.6)
18:06:46*crem joined #nim
18:12:21FromGitter<awr1> @shashlick thanks!
18:12:23FromGitter<awr1> may use this
18:14:52*laaron quit (Quit: ZNC 1.7.1 - https://znc.in)
18:15:10*laaron joined #nim
18:16:08*btop quit (Ping timeout: 245 seconds)
18:19:38*btop joined #nim
18:27:38FromGitter<awr1> actually i like the idea of being able to link this totally dynamically
18:29:48FromGitter<awr1> i hate having to add more `passL` stuff and the whole well - this is less of an issue with xcb and more c libraries in general - the whole issue of "did you get the static developer libaries" that comes with c dependencies
18:31:53FromGitter<awr1> it would be ideal to just have to say: "oh, i need a dependency? let me just grab a lib from nimble and import a module." without having to worry about the extraneous stuff
18:33:03Araqyou just described Nim's default mode of working...
18:33:47FromGitter<awr1> i mean, yeah, that's the experience i've had, barring a few exceptions
18:36:55shashlickthat's what i'm trying to do
18:37:46FromGitter<awr1> i think one of the first things i tried to make with nim was something using oldwinapi and i was pleasantly surprised i didn't have to wrangle in any crap with libgdi32 or something
18:49:14*btop quit (Ping timeout: 240 seconds)
18:50:47*blu joined #nim
19:20:29ZevvIs it likely that dotOperators will move out of experimental before 1.0?
19:27:13AraqZevv: what do you think? https://github.com/nim-lang/Nim/milestone/2
19:28:57*couven92 joined #nim
19:39:15ZevvI think There are no open issues in this milestone
19:39:23Zevvcongrats on that, by the way :)
19:40:12Zevvlast one was closed 11 days ago, and no party was thrown?!
19:40:24*absolutejam1 joined #nim
19:40:28narimiranZevv: it's just that you weren't invited :P :D
19:40:43ZevvThat's what you get when you dont facebook
19:41:37Zevvbtw narimiran, is this murmur related? https://forum.nim-lang.org/t/5189
19:41:51Zevvno way to tell without seeing this guys data set of course, but still
19:43:07narimiran"the default (...) uint64 hash function was likely to blame" — https://github.com/nim-lang/Nim/blob/devel/lib/pure/hashes.nim#L127
19:43:13FromGitter<brentp> i think it is hash related. i suggested to him (via other channels) to hash his own input and that resolved the issue.
19:43:20FromGitter<brentp> he said that updating to devel did not fix.
19:44:21FromGitter<brentp> i guess that makes sense given your link.
19:45:02Zevvthat's kind of funny, actually
19:45:23Zevva bit like the random '4'. it's not *wrong*
19:45:28Zevvand it *is* efficient
19:47:51FromGitter<brentp> very
19:47:58*rockcavera joined #nim
19:48:05Zevvbah: Error: VM problem: too many registers required
19:48:11*rockcavera quit (Remote host closed the connection)
19:48:31*rockcavera joined #nim
19:55:37AraqZevv: write/generate smaller compileTime procs
19:56:02Araqeventually the VM gen should implement spilling though to resolve this problem
19:58:26ZevvAraq: generated code
19:58:38AraqI know
19:58:53Zevvwell, it's just a silly experiment, so no problem for now
20:00:48*narimiran quit (Remote host closed the connection)
20:04:27shashlickcan you make cmake run in parallel? its so slow
20:05:15Calinouwhere are you using CMake? are you generating multiple projects at once?
20:08:02shashlickon windows - running it for zlib and libarchive
20:08:11shashlicki have many cores available but it just runs in sequence
20:13:15Zevvyou're referring to the actuall *cmake* run right, not to the *make* you're doing for compiling?
20:13:44shashlickyes correct
20:13:53Zevvout of luck, afaik
20:14:11shashlickim already running make with -j after detecting # of cores
20:14:11Zevvcmake is just sequential. It's about as stupid as a shell script
20:14:16Zevvbut less documented and harder to debug
20:14:37*Zevv loathes cmake
20:14:38shashlicknow i'm just getting could not load x.dll
20:14:42*wildtrees left #nim ("Leaving")
20:14:43shashlickgetting fed up
20:18:44Calinouyou can use CMake with Ninja to make your builds faster, but there's nothing you can really do to speed up generation, I'm afraid
20:18:50Calinou(except not doing it when you don't need to :P)
20:19:05Calinoualso, this might be worth keeping around: https://cliutils.gitlab.io/modern-cmake/
20:19:10Calinou(found it while searching for a solution)
20:21:41Calinouaccording to a comment in https://stackoverflow.com/questions/26701628/cmake-is-slow-to-generate-makefiles, Ninja files are also faster to generate compared to Makefiles
20:23:34Zevvlet's parse some C: http://ix.io/1V1l
20:23:47*rockcavera quit (Read error: Connection reset by peer)
20:24:05*rockcavera joined #nim
20:24:05*rockcavera quit (Changing host)
20:24:05*rockcavera joined #nim
20:24:41Calinouthere's also https://cristianadam.eu/20170709/speeding-up-cmake/ but it looks fairly involved
20:24:52*btop joined #nim
20:31:41*couven92 quit (Ping timeout: 246 seconds)
20:33:28*nsf joined #nim
20:34:38*abm quit (Quit: Leaving)
20:35:40FromGitter<xmonader> https://forum.nim-lang.org/t/5190#32550
20:36:47FromGitter<xmonader> is there a way to unpublish packages from nimble index?
20:37:21ZevvPR the packages repo
20:37:35Zevvremove the project from the json
20:41:26FromGitter<alehander42> why would you unpublish
20:41:48*huj123[m] quit (Read error: Connection reset by peer)
20:41:49*GitterIntegratio quit (Write error: Connection reset by peer)
20:41:50*xomachine[m] quit (Read error: Connection reset by peer)
20:41:54*Demos[m] quit (Read error: Connection reset by peer)
20:41:55*nergal[m] quit (Read error: Connection reset by peer)
20:41:55*narimiran[m] quit (Read error: Connection reset by peer)
20:41:58*BitPuffin quit (Read error: Connection reset by peer)
20:42:02*leorize[m] quit (Remote host closed the connection)
20:42:06*macsek1911[m] quit (Remote host closed the connection)
20:42:10*planetis[m] quit (Remote host closed the connection)
20:42:12*encryptize[m] quit (Read error: Connection reset by peer)
20:42:13*spymasterd[m] quit (Read error: Connection reset by peer)
20:42:15*meff[m] quit (Read error: Connection reset by peer)
20:42:16*gh0st[m] quit (Write error: Connection reset by peer)
20:42:17*skrylar[m] quit (Read error: Connection reset by peer)
20:42:18*zielmicha[m]1 quit (Read error: Connection reset by peer)
20:42:19*LEdoian[m] quit (Write error: Connection reset by peer)
20:42:20*yglukhov[m] quit (Read error: Connection reset by peer)
20:42:20*isaac[m]1 quit (Read error: Connection reset by peer)
20:42:20*Miguelngel[m] quit (Remote host closed the connection)
20:42:20*pigmej[m] quit (Write error: Connection reset by peer)
20:42:21*jaens[m] quit (Remote host closed the connection)
20:42:21*k0mpjut0r quit (Write error: Connection reset by peer)
20:42:22*muxueqz[m] quit (Remote host closed the connection)
20:42:22*Connor[m] quit (Remote host closed the connection)
20:42:23*TheManiac[m] quit (Write error: Connection reset by peer)
20:42:23Zevv" refuse to be part of some biased unclear scoring system that threatens to remove my packages"
20:42:56FromGitter<alehander42> but i dont even think this
20:43:01FromGitter<alehander42> this is just a 3rd person effort
20:43:04FromGitter<alehander42> right
20:43:17FromGitter<alehander42> everybody is free to do its own rankings
20:43:23FromGitter<alehander42> and scoring systems
20:43:30Araqxmonader: please don't remove your packages :-(
20:43:42FromGitter<alehander42> i dont see anything about removal
20:48:07FromGitter<xmonader> "While we really appreciate your contribution, please follow the requirements: other developers will rely on your package. Non-compliant packages might be removed with no warning."
20:49:32Zevvthat's from the packages repo, has nothing to do with this rating initiative afaik?
20:50:05*Connor[m] joined #nim
20:51:21FromGitter<xmonader> @Zevv if it's for package.json fields if they're reviewed when u do nimble publish before merging them to the index already no?
20:54:54FromGitter<alehander42> i really think this is more about malicious code or something like that
20:56:24FromGitter<xmonader> and non mature packages too github.com/pmetras/packages/blob/extended_info/README.md
20:59:49*cgfuh quit (Quit: WeeChat 2.5)
21:08:00FromGitter<alehander42> i dont really see how something like this scales
21:08:32FromGitter<alehander42> it might work for a small ecosystem, but i can't imagine it for bigger ecosystems with 100_000 of packages
21:08:48FromGitter<alehander42> without a dedicated person/team
21:09:05FromGitter<alehander42> which might be fine for such ecosystems , so maybe it scales manually
21:10:01FromGitter<alehander42> but still, i dont see anything about removal of "non-mature" packages
21:10:24FromGitter<alehander42> only about marking them as such
21:10:43FromGitter<alehander42> otherwise it's a interesting idea, to have such a system
21:12:28*Demos[m] joined #nim
21:12:28*TheManiac[m] joined #nim
21:12:28*BitPuffin joined #nim
21:12:28*LEdoian[m] joined #nim
21:12:29*k0mpjut0r joined #nim
21:12:29*GitterIntegratio joined #nim
21:12:29*planetis[m] joined #nim
21:12:29*isaac[m]1 joined #nim
21:12:30*nergal[m] joined #nim
21:12:30*jaens[m] joined #nim
21:12:30*leorize[m] joined #nim
21:12:30*pigmej[m] joined #nim
21:12:30*gh0st[m] joined #nim
21:12:35*encryptize[m] joined #nim
21:12:36*yglukhov[m] joined #nim
21:12:36*macsek1911[m] joined #nim
21:12:36*xomachine[m] joined #nim
21:12:36*narimiran[m] joined #nim
21:12:36*Miguelngel[m] joined #nim
21:12:36*spymasterd[m] joined #nim
21:12:37*muxueqz[m] joined #nim
21:12:37*zielmicha[m]1 joined #nim
21:12:37*meff[m] joined #nim
21:12:37*skrylar[m] joined #nim
21:12:38*lqdev[m] joined #nim
21:15:23*solitudesf quit (Ping timeout: 276 seconds)
21:16:19FromGitter<xmonader> marked as in what? that's in nimble publish phase or afterwards? who would set that? does it depend on code/doc/proj quality fields? who should set them is it the author? or is it nimble team? is marked means to be solved in the `nimble publishing` process or not? what happens to the packages that score less than the `mature` level in the current index?
21:17:34FromGitter<alehander42> good questions, but let's just wait for an answer from the author
21:17:59FromGitter<alehander42> in any case, i dont think any existing used packages will be removed
21:31:11*btop quit (Ping timeout: 246 seconds)
21:45:34*lqdev[m] is now known as huj123[m]
21:58:08*Kaivo quit (Quit: WeeChat 2.5)
22:05:14*btop joined #nim
22:08:45*krux02 joined #nim
22:11:01*btop quit (Ping timeout: 268 seconds)
22:11:32*krux02 quit (Remote host closed the connection)
22:30:46*krux02 joined #nim
22:40:31*thomasross quit (Remote host closed the connection)
22:40:59*thomasross joined #nim
22:55:55*krux02 quit (Remote host closed the connection)
22:56:50*absolutejam1 quit (Ping timeout: 276 seconds)
22:57:14*NimBot joined #nim
22:57:53rockcaveraDoesn't Nim have the unary operator "minus" for unsigned integer?
22:59:13*absolutejam1 joined #nim
23:03:19*NotCreative quit (Ping timeout: 260 seconds)
23:04:35*absolutejam1 quit (Ping timeout: 276 seconds)
23:16:41*notcreative joined #nim
23:22:08*ng0 quit (Ping timeout: 260 seconds)
23:26:35*ng0 joined #nim
23:28:55*thomasross_ joined #nim
23:28:55*thomasross is now known as Guest57320
23:28:55*Guest57320 quit (Killed (weber.freenode.net (Nickname regained by services)))
23:28:55*thomasross_ is now known as thomasross
23:29:22FromGitter<mratsim> No
23:29:36FromGitter<mratsim> You can implement it youself
23:29:56FromGitter<mratsim> not(n) + 1 will do unary minus
23:30:05FromGitter<mratsim> GCC should compile it to neg
23:30:30FromGitter<mratsim> unary minus is C unsafe type casting
23:32:42*nsf quit (Quit: WeeChat 2.5)
23:53:19*btop joined #nim
23:58:56*btop quit (Ping timeout: 268 seconds)