<< 01-11-2021 >>
00:00:13*tk quit (Quit: Well, this is unexpected.)
00:00:37*tk joined #nim
00:19:00FromDiscord<tandy> can you compile a nim project for windows on a linux machine without a vm?
00:19:12FromDiscord<Elegantbeef> get mingw and possibly
00:19:24FromDiscord<Elegantbeef> pass `-d:mingw` and let 'er rip
00:22:07FromDiscord<tandy> oo leme see what the fedora package is
00:26:43FromDiscord<tandy> nice that seemed to make an exe
00:26:48FromDiscord<tandy> hopefuly it works lol
00:28:16FromDiscord<Elegantbeef> Doing more than the Rust game devs did for the linux build
00:31:46FromDiscord<tandy> lol
00:39:53FromDiscord<OceanMongrel> This might be a stupid question, but is there a way to write functions in swift, which can be used by min? Is there any way the two languages can interact resulting in a single executable?
00:40:07FromDiscord<Elegantbeef> Min or Nim?
00:40:15FromDiscord<OceanMongrel> sorry, nim
00:40:30FromDiscord<Elegantbeef> Min is a language made with Nim so it wasnt a joke πŸ˜€
00:41:53FromDiscord<Elegantbeef> Well you can write libraries using either then connect them using dynamic library mechanicism much like if you wrote the code in C
00:42:27FromDiscord<retkid> anyway to use curly braces in nim?
00:42:37FromDiscord<Elegantbeef> That'd probably require writing some tooling to make it easier to access code from Nim and Swift
00:42:48FromDiscord<Elegantbeef> Yea for sets πŸ˜›
00:43:00FromDiscord<Elegantbeef> Otherwise no you need to customize your editor or preprocess the file
00:43:15FromDiscord<Elegantbeef> https://github.com/treeform/genny for a reference of the type of thing you'd probably want ocean
00:43:27FromDiscord<retkid> god damn treeform is everwhere
00:43:32FromDiscord<retkid> such a talented mofo
00:43:59FromDiscord<OceanMongrel> Thanks! I'll look into it
00:44:05FromDiscord<Elegantbeef> Now to down play him but he's afterall a dev that uses Nim full time so kinda the expected
00:44:10FromDiscord<Elegantbeef> not to\
03:02:11*neurocyte0132889 quit (Ping timeout: 264 seconds)
03:10:17*arkurious quit (Quit: Leaving)
03:12:07*vicecea quit (Remote host closed the connection)
03:12:38*vicecea joined #nim
03:19:58FromDiscord<joe733> Hi, what would be the Nim equivalent of `[False] 3` which gives `[False, False, False]` in Python?
03:22:14FromDiscord<Elegantbeef> you can do `import std/sequtils; newSeqWith[bool](3, true)` or given false is default for bool `newSeq[bool](3)`
03:22:16FromDiscord<huantian> I think it would be `newSeqWith` from sequtils
03:22:21FromDiscord<huantian> sniped
03:22:22FromDiscord<Elegantbeef> Assuming you want a seq
03:22:51FromDiscord<Elegantbeef> If you want an array there are no builtin shortcuts
03:23:38FromDiscord<Elegantbeef> Although again `var a: array[3, bool]` would give false
03:29:24FromDiscord<joe733> Thanks!
03:30:08FromDiscord<Elegantbeef> No problem
03:44:27FromDiscord<demotomohiro> !eval echo default(array[3, bool])
03:44:29NimBot[false, false, false]
03:58:34FromDiscord<impbox [ftsf]> if you want truth you're less lucky
03:58:52FromDiscord<impbox [ftsf]> but lies are free!
04:06:01*supakeen quit (Quit: WeeChat 3.3)
04:06:31*supakeen joined #nim
04:43:28FromDiscord<evoalg> if it's a seq, then I could import sequtils and do `@[true].cycle(3)` if I wanted the truth ... it's kind of the equivalent of python's `[True] 3`
04:57:22FromDiscord<Rika> repeat represents the intent better
04:59:15FromDiscord<evoalg> 'true.repeat(3)' you're right!
05:00:28FromDiscord<Rika> cycle is for repeating seqs into a flattened seq
05:00:51FromDiscord<Rika> so @[1, 2, 3].cycle(3) => @[1,2,3,1,2,3,1,2,3]
05:04:43*rockcavera quit (Remote host closed the connection)
05:05:27FromDiscord<evoalg> I'm still impressed that collect can replicate almost every proc in sequtils ... collect is so powerful
05:05:32FromDiscord<Rika> it is
05:05:50FromDiscord<Rika> less stupid to read as well compared to list comprehensiosn
05:06:27FromDiscord<evoalg> absolutely ... it may sound strange but collect is one of the best things about nim for me
05:07:36FromDiscord<Rika> anything with two or more nested loops should not be a comprehension but so many people do it anyway so πŸ˜„
05:10:45FromDiscord<evoalg> I've done it many times, and it's so unreadable. In python with the for loops and the if's at the end, and then the "if else" being hacked into the syntax later, but it has be before the for loops, then nested LC's it quickly becomes so unreadable
05:13:04FromDiscord<evoalg> whoever came up with collect, thank you
05:19:19FromDiscord<Elegantbeef> Yea collect is the more readable and proper left to right top to bottom evaluation
05:27:29FromDiscord<evoalg> I'm trying to echo a 2D seq so it prints one "row" per line, and I can do that in a loop, but in python I would use pprint as it's quick ... I tried "print" but that's not what I want, should I just stick to the for loop?
05:29:14FromDiscord<Elegantbeef> You could do that or make your own `$` or `rowPrint` which either gives you a string or prints it for you
05:29:25FromDiscord<Elegantbeef> But yea pretty much the best way to do it is loop πŸ˜€
05:31:12FromDiscord<evoalg> loop is fine, thank you!
05:54:12*robertmeta quit (*.net *.split)
05:54:13*Onionhammer quit (*.net *.split)
05:54:13*crem quit (*.net *.split)
05:54:13*mjsir911 quit (*.net *.split)
05:54:29*robertmeta joined #nim
05:54:30*crem joined #nim
05:54:31*Onionhammer joined #nim
05:54:31*mjsir911 joined #nim
05:54:42*mjsir911 quit (Changing host)
05:54:42*mjsir911 joined #nim
06:02:51*skrzyp quit (*.net *.split)
06:03:12*skrzyp joined #nim
06:50:04FromDiscord<evoalg> actually as the 2D seq grows larger, print automatically puts it in a nice format if it would otherwise hit the end of the terminal window, whereas echo just wraps, so I'm quite happy with "print"
06:59:51FromDiscord<treeform> In reply to @evoalg "I'm trying to echo": I am not sure what "print" you are talking about but I have my "print" that works kind of like pretty print from python: https://github.com/treeform/print
07:00:23FromDiscord<evoalg> yep I'm using yours ... I nimble installed it ... thank you for that print!
07:01:01FromDiscord<treeform> cool, thank you for using it
07:01:59FromDiscord<treeform> I should document it but I recently added printTable which might work even better for priting seqs.
07:02:23FromDiscord<evoalg> ooooo sounds nice
07:02:55FromDiscord<treeform> https://media.discordapp.net/attachments/371759389889003532/904626538861973524/unknown.png
07:03:35FromDiscord<Rika> Nice
07:04:04FromDiscord<treeform> instead of: https://media.discordapp.net/attachments/371759389889003532/904626828524793887/unknown.png
07:04:50FromDiscord<evoalg> I'm not sure it likes my seq[seq[char]] though
07:05:03FromDiscord<treeform> yeah probably not πŸ™‚
07:05:03FromDiscord<evoalg> it's mean for tables right?
07:05:10FromDiscord<evoalg> okay
07:05:21FromDiscord<treeform> its mean for seq of objects
07:05:36FromDiscord<treeform> for seq[seq[char]] you want some sort of grid almost
07:05:36FromDiscord<evoalg> ahh yep ... makes sense
07:05:55FromDiscord<evoalg> print seems to suit really nicely
07:05:57FromDiscord<evoalg> for it
07:06:01FromDiscord<treeform> ok cool
07:06:37FromDiscord<evoalg> and colors just work, very cool
07:11:08FromDiscord<treeform> nice
07:18:10FromDiscord<evoalg> That dark blue that print prints is hard to read on my dark terminal, but maybe that's my terminal color scheme
07:18:42FromDiscord<treeform> I am sure you can play around with your settings. I am just using the 8 primary terminal colors.
07:19:01FromDiscord<evoalg> sound good!
07:23:56FromDiscord<evoalg> sorted!
08:27:23*kayabaNerve quit (Remote host closed the connection)
08:27:41*kayabaNerve joined #nim
08:31:46*Vladar joined #nim
08:35:09*kayabaNerve quit (Remote host closed the connection)
08:35:44*kayabaNerve joined #nim
08:36:49*kayabaNerve quit (Remote host closed the connection)
08:37:09*kayabaNerve joined #nim
08:39:11*kayabaNerve quit (Remote host closed the connection)
08:41:27*PMunch joined #nim
10:04:17PMunchThis post raises an interesting question. With default Table initialisation maybe it makes sense to have something like this in the official tables module? https://forum.nim-lang.org/t/8568#55665
10:30:49FromDiscord<Rika> https://www.lightbluetouchpaper.org/2021/11/01/trojan-source-invisible-vulnerabilities/
10:35:08FromDiscord<Rika> Vulnerability that affects essentially all programming languages as it is based on the source and its rendering and not the code
10:36:43supakeenA story as old as escape sequences in the shell.
10:36:51supakeenBut good to renew exposure into it.
10:36:51FromDiscord<enthus1ast> bak in the days we've used this / or similar tricks in filenames
10:37:09supakeenIt was always one of the main things for filenames and/or all those curl ... | sh things that they might contains escapes.
10:39:03NimEventerNew thread by Lachu: [Imageman][nimgl] Loading texture, see https://forum.nim-lang.org/t/8571
11:14:55PMunchHuh, I've seen this for use in phishing attempts to create domains that look similar to the real domain but actually contains homoglyphs
11:15:05PMunchBut interesting to see it be used for code
11:17:12PMunchMaybe we should set up our editors to use semantic highlighting and pick different colours for different variables
12:06:02*supakeen quit (Quit: WeeChat 3.3)
12:06:32*supakeen joined #nim
12:07:30NimEventerNew thread by Monyarm: Is there any way to check if a type is distinct?, see https://forum.nim-lang.org/t/8572
12:23:32NimEventerNew thread by Gyohng: Is there a multithreaded HTTP library?, see https://forum.nim-lang.org/t/8573
12:28:14madpropswhen using `pairs` required to get index,value ?
12:28:24madpropswhen is*
12:30:41FromDiscord<haxscramper> it is required when you need to get index and value? Or you mean when it has to be called explicitly?
12:31:03FromDiscord<haxscramper> usually you don't need to call it explicitly, but sometimes I do for the sake of explicitness
12:31:19madpropsyeah I meant explicitly
12:32:06FromDiscord<enthus1ast> i just flawlessly interopted with nim from a Lazarus gui, nice
12:32:18FromDiscord<Rika> you can call it explicitly with a single var for loop to have a tuple instead in that var
12:32:26FromDiscord<Rika> `for tpl in a.pairs():`
12:32:27FromDiscord<Rika> or so
12:33:33NimEventerNew thread by Gyohng: This forum preview JS error, see https://forum.nim-lang.org/t/8574
12:34:32FromDiscord<enthus1ast> maybe this will be my new "secret weapon" for ultra fast guis
12:35:14FromDiscord<enthus1ast> ultra fast in the sence of clicking them together, build the most heavy lifting logic in nim then ship
12:35:50FromDiscord<Rika> what is lazarus
12:36:18FromDiscord<enthus1ast> a Ide for freepascal like Delphi (but actually cross platform\: Win, Mac, Linux)
12:36:44FromDiscord<enthus1ast> i know pascal is not sexy \:)
12:37:00FromDiscord<enthus1ast> but actually nim shares a lot of its ideas with pascal
12:37:17FromDiscord<enthus1ast> the first compiler was build in pascal by araq iirc
12:41:40FromDiscord<enthus1ast> maybe not `ideas`, but it looks more like nim than eg c
12:42:22FromDiscord<enthus1ast> looks familiar right?
12:42:22FromDiscord<enthus1ast> sent a code paste, see https://play.nim-lang.org/#ix=3DAO
12:48:58FromDiscord<Rika> i know that nim shares a lot with pascal, i just didnt know what lazarus was
12:49:35NimEventerNew thread by Gyohng: Query nim include paths, see https://forum.nim-lang.org/t/8575
12:49:39FromDiscord<enthus1ast> tl;dr an ide and (mostly gui) class library
12:49:45FromDiscord<enthus1ast> for freepascal
12:49:49FromDiscord<Rika> cool
12:51:00FromDiscord<Yardanico> In reply to @enthus1ast "tl;dr an": there are libs that wrap lcl in different languages, for example one in go - https://github.com/ying32/govcl
12:51:37FromDiscord<Yardanico> he also made https://github.com/ying32/nim-vcl but it's archived
12:51:53FromDiscord<Yardanico> @enthus1ast you might be interested in this one anyway ^
12:52:10FromDiscord<enthus1ast> yes, thank you
12:52:42FromDiscord<Yardanico> 1.5mb source files though :DD
12:52:55FromDiscord<enthus1ast> currently if i need crossplatform gui i use python/tk ... bundled with pyinstallert
12:53:15FromDiscord<enthus1ast> and i hate it every time i do it \: )
12:59:59*kayabaNerve joined #nim
13:02:11*kayabaNerve_ joined #nim
13:04:54*kayabaNerve quit (Ping timeout: 260 seconds)
13:05:18*kayabaNerve_ is now known as kayabaNerve
13:06:24*Vladar quit (Remote host closed the connection)
13:15:01*krux02 quit (Remote host closed the connection)
13:24:31FromDiscord<cabboose> sup party people
13:25:35*arkurious joined #nim
13:25:46FromDiscord<Rika> learning nixos to set up some (nim) web services + gitea+ci for such services
13:25:51FromDiscord<Rika> you
13:26:03FromDiscord<Rika> (edit) "learning" => "(re)learning"
13:26:14FromDiscord<cabboose> Considering whether to watch DUNE or not
13:26:22FromDiscord<cabboose> so, not as productive
13:26:39FromDiscord<Rika> oh dude you dont want to try to be "as productive" as me
13:26:48FromDiscord<Rika> ive been going on this journey nonstop for weeks now
13:26:57FromDiscord<Rika> im prolly burnt out but im obsessed with getting this working
13:27:29FromDiscord<cabboose> Oh yeah I'm already burnt out. I've literally been told by a health professional to play games and "have fun"
13:27:40FromDiscord<cabboose> and that obsession
13:27:43FromDiscord<cabboose> thats the one that does it
13:27:45FromDiscord<cabboose> save yourself rika
13:27:45FromDiscord<Rika> i dread working on it but i keep on searching info about how to do it in my spare time, idfk why the fuck i do that
13:27:47FromDiscord<cabboose> while you still can
13:27:53FromDiscord<IsaacPaul> my fun is programming
13:27:55FromDiscord<IsaacPaul> xD
13:27:59FromDiscord<Rika> NO
13:28:00FromDiscord<Rika> DONT SAY THAT
13:28:05FromDiscord<cabboose> It's fun until its not fun
13:28:12FromDiscord<Rika> THATS LITERALLY WHY IVE BEEN WORKING ON THIS FOR SO LONG
13:28:22FromDiscord<IsaacPaul> that and going to breweries
13:28:46FromDiscord<cabboose> Programming is my fun too; the issue is nothing is fun anymore
13:28:46FromDiscord<Rika> are all programmers alcohol abusers because i feel like im not a programmer until i do so
13:29:09FromDiscord<cabboose> In reply to @Rika "are all programmers alcohol": if the people I talk to are anything to go by it seems like you have to abuse something
13:29:14FromDiscord<cabboose> like beef abuses himself
13:29:19FromDiscord<IsaacPaul> I used to, I've cut back. I feel not as 'sharp' anymore and I don't want it to effect my programming
13:29:21FromDiscord<cabboose> so it doesnt have to be alcohol? I guess?
13:29:22FromDiscord<Rika> i guess i am already there
13:30:06PMunch@cabboose, can highly recommend Dune
13:30:10FromDiscord<Rika> In reply to @IsaacPaul "I used to, I've": basically we (read: i) need to learn about what makes us (read: me) obsess over stuff like this
13:30:16FromDiscord<cabboose> alright im starting it
13:30:18FromDiscord<cabboose> cheers cobba
13:30:47FromDiscord<cabboose> In reply to @Rika "basically we (read: i)": If you want to answer some questions with me I can do a screening on that
13:30:58FromDiscord<Rika> wdym
13:31:03FromDiscord<IsaacPaul> It's the effort -> reward process imo
13:31:05FromDiscord<Rika> me no english native me no understand
13:31:29FromDiscord<cabboose> You know a psychology questionnaire that helps to show how someones brain works
13:31:32FromDiscord<Rika> what questions? screen what?
13:31:33FromDiscord<Rika> oh
13:31:45FromDiscord<Rika> yeah i havent taken any of those in my life i believe
13:31:53FromDiscord<cabboose> Not many people have hahaha
13:37:05FromDiscord<Steffen> Hello peoples
13:37:21FromDiscord<Steffen> Suppose Im trying to get C library working via FFI
13:37:38FromDiscord<Steffen> I have a function now that returns NULL on error
13:37:43FromDiscord<Steffen> How would I check for that?
13:39:45FromDiscord<Rika> NULL and nil are the same afaik?
13:40:55FromDiscord<Steffen> that would be nice
13:41:45FromDiscord<IsaacPaul> they're different in obj-c , not sure about nim. ↡I'm assuming you're getting a zeroed pointer back so whatever return value that is a pointer should work..
13:42:44FromDiscord<Steffen> mhh
13:43:29FromDiscord<IsaacPaul> I can test and see
13:44:00FromDiscord<haxscramper> `let returnValue = function()` followed by `isNil(returnValue)`↡(@Steffen)
13:44:17FromDiscord<haxscramper> there is no such thing as NULL in C, it is just a macro that expands to 0 or something along those lines
13:44:25FromDiscord<haxscramper> so you just get null pointer
13:44:29FromDiscord<hips> I like a beer on Friday night, that's about it πŸ˜…
13:45:24FromDiscord<Steffen> yeah, null pointer
13:46:36FromDiscord<Steffen> trying to get ldap working
13:46:45FromDiscord<Steffen> "If an error occurs, ldap_open() and ldap_init() will return NULL and errno should be set appropriately. "
13:46:52FromDiscord<Steffen> https://www.openldap.org/software/man.cgi?query=ldap_initialize&apropos=0&sektion=3&manpath=OpenLDAP+2.5-Release&arch=default&format=html
13:47:13FromDiscord<Steffen> Been a few years since I messed with C. But looks doable
13:47:47FromDiscord<dom96> basically the only time I drink alcohol is at FOSDEM, but I think we should discuss such things in #offtopic
13:48:42FromDiscord<Rika> how do people wrap errno stuff in C?
13:51:39FromDiscord<IsaacPaul> sent a code paste, see https://play.nim-lang.org/#ix=3DBc
13:51:47FromDiscord<IsaacPaul> (edit) "https://play.nim-lang.org/#ix=3DBc" => "https://play.nim-lang.org/#ix=3DBd"
13:52:43FromDiscord<IsaacPaul> In reply to @Rika "how do people wrap": Good question πŸ˜†
13:53:44FromDiscord<IsaacPaul> sent a code paste, see https://play.nim-lang.org/#ix=3DBe
13:54:29FromDiscord<IsaacPaul> disregard the attribute stuff, but idk if that will break things.. :S
13:57:45FromDiscord<Steffen> mhh, Im getting a not null back
13:59:20PMunch@Rika, depends on what you mean by wrap
13:59:38FromDiscord<Rika> translate the interface for nim
14:00:59PMunchI guess the "proper" way would be to have an exception type like CError which has an errno field and then have wrappers like `errno = 0; <actual call>; if errno != 0: raise CError(errno: errno, msg: <call to convert errno to string>)`
14:05:23FromDiscord<Steffen> oh wow
14:05:29FromDiscord<Steffen> looks like its working
14:05:44NimEventerNew thread by Benob: Nim's version of the Trojan Source vulnerability, see https://forum.nim-lang.org/t/8576
14:12:03FromDiscord<Steffen> I hate ldap
14:13:49FromDiscord<IsaacPaul> In reply to @IsaacPaul "On a import c": Nevermind, found some example code on github πŸ˜„ ↡https://github.com/numforge/laser/blob/master/laser/simd.nim#L21↡Really loving the built in vscode in github (via `.` )
14:24:16FromDiscord<Steffen> How can I set a pointer to an int?
14:24:19FromDiscord<Steffen> first type mismatch at position: 3↡ required type for invalue: ptr cint↡ but expression '"3"' is of type: string
14:25:51FromDiscord<Yardanico> well, it seems like you're passing a string where the proc expects a pointer to an int. Can you show the proc definition and tell where the actual function comes from?
14:25:57FromDiscord<enthus1ast> pardon
14:25:58FromDiscord<enthus1ast> var ii\: cint
14:26:02FromDiscord<enthus1ast> sent a code paste, see https://play.nim-lang.org/#ix=3DBy
14:26:27FromDiscord<Yardanico> sent a code paste, see https://play.nim-lang.org/#ix=3DBz
14:26:35FromDiscord<Yardanico> (edit) "https://play.nim-lang.org/#ix=3DBz" => "https://play.nim-lang.org/#ix=3DBA"
14:26:58FromDiscord<Steffen> https://www.openldap.org/software/man.cgi?query=ldap_set_option&apropos=0&sektion=3&manpath=OpenLDAP+2.6-Release&arch=default&format=html
14:27:05FromDiscord<Steffen> proc ldap_set_option(ld: ptr LDAP; option: cint; invalue: ptr cint): cint
14:28:02FromDiscord<Yardanico> oh, then the proc definition is wrong
14:28:11FromDiscord<Yardanico> it should just be `invalue: pointer`
14:28:15FromDiscord<Steffen> yes and no
14:28:24FromDiscord<Yardanico> ?
14:28:49FromDiscord<Steffen> Depends on Option
14:28:50FromDiscord<Steffen> LDAP_OPT_PROTOCOL_VERSION↡ Sets/gets the protocol version. outvalue and invalue must be↡ int .
14:29:22FromDiscord<Yardanico> yes, but again, your proc shouldn't make assumptions of specific argument types, they say it's `void` so you should use `pointer`
14:29:29FromDiscord<Yardanico> and of course you'll be able to pass `ptr cint` to it
14:29:36FromDiscord<Yardanico> because `ptr cint` is compatible with `pointer`
14:30:24FromDiscord<Yardanico> sent a code paste, see https://play.nim-lang.org/#ix=3DBB
14:31:09FromDiscord<Steffen> yeah, thank you. that compoled
14:31:12FromDiscord<Steffen> compiled too
14:34:27FromDiscord<Steffen> root@fd1b95a338cc:/ssh-ldap# ./ffi↡Not null↡0↡Success
14:34:32FromDiscord<Steffen> I like success
14:35:10FromDiscord<Rika> who doesnt
14:37:40FromDiscord<tandy> i just saw nimskull
14:37:49FromDiscord<Rika> πŸ’€
14:37:50FromDiscord<tandy> thought it might be from [haxscramper](https://matrix.to/#/@haxscramper:matrix.org)
14:38:10FromDiscord<Yardanico> it's from saem
14:38:14FromDiscord<Yardanico> and othjers
14:38:19FromDiscord<Yardanico> (edit) "othjers" => "others"
14:38:20FromDiscord<haxscramper> it's from multiple people
14:38:27FromDiscord<Yardanico> exactly
14:38:51*neurocyte0132889 joined #nim
14:38:51*neurocyte0132889 quit (Changing host)
14:38:51*neurocyte0132889 joined #nim
14:40:25FromDiscord<haxscramper> how do you like roadmap on the readme btw?
14:41:26FromDiscord<Arend | α›—α›Ÿαš’αš±α›α›–α›Š> I have a suggestion for the roadmap 😏
14:41:54FromDiscord<Rika> lets hear it
14:43:34FromDiscord<tandy> \:\>) very nice
14:44:10FromDiscord<xflywind> In reply to @haxscramper "how do you like": So eventually `nim-works/cps` will abandon Nim?
14:44:45FromDiscord<Rika> probably not?
14:45:01FromDiscord<haxscramper> define "abandon"
14:45:32FromDiscord<haxscramper> we don't want to keep ten years work of backwards compat hacks, barely working impls for two concepts, shit like coreReordering and so on
14:45:56FromDiscord<haxscramper> at the same time breaking for the sake of breaking is not a goal either
14:46:22FromDiscord<haxscramper> right now we want working compiler
14:46:58*neurocyte0132889 quit (Read error: Connection reset by peer)
14:47:06FromDiscord<Rika> i think they mean you'll abandon cps on nim in favor of maintaining cps for skull
14:50:27FromDiscord<haxscramper> and one that can be easily contributed to
14:50:30FromDiscord<haxscramper> and language specification
14:50:44FromDiscord<xflywind> In reply to @Rika "i think they mean": yeah, it's painful to maintain two incompatible compiler
14:50:52FromDiscord<xflywind> (edit) "compiler" => "compilers"
14:51:08FromDiscord<Yardanico> you mean to maintain a library for two compilers
14:51:17FromDiscord<haxscramper> cps is a main reason of "we want working compiler"
14:52:14FromDiscord<xflywind> I see
14:52:41*neurocyte0132889 joined #nim
14:52:41*neurocyte0132889 quit (Changing host)
14:52:41*neurocyte0132889 joined #nim
14:52:45FromDiscord<haxscramper> well, if you want to know my personal opinion on that one
14:52:49*Lord_Nightmare quit (Quit: ZNC - http://znc.in)
14:53:15FromDiscord<haxscramper> I would prefer to put my effort into project where I know what are goals and plans are
14:53:33FromDiscord<haxscramper> But I don't personally want to rewrite all my code either
14:54:01*Lord_Nightmare joined #nim
14:54:21FromDiscord<haxscramper> You can see it as nim 2.0 if you want
14:55:49NimEventerNew thread by IvanS: Fidget questions - 1) scrolling - 2) closing window, see https://forum.nim-lang.org/t/8577
14:56:44*PMunch quit (Quit: Leaving)
15:05:49FromDiscord<tandy> how far apart will nim and nimskull be? i see you have bors for getting commits from the nim repo but i guess it will be hard to tell whether araq etc will keep going or join the nimskull effort?
15:11:31*neurocyte0132889 quit (Ping timeout: 268 seconds)
15:12:02*neurocyte0132889 joined #nim
15:12:02*neurocyte0132889 quit (Changing host)
15:12:02*neurocyte0132889 joined #nim
15:27:49FromDiscord<leorize> what does bors have to do with getting commits from nim repo? \:p
15:32:03FromDiscord<leorize> anyway, I wouldn't expect nimskull to deviate too far from nim
15:33:52FromDiscord<leorize> for most meaningful purposes, as far as I can tell, because Nim's ecosystem is something that nimskull will have to play nice with
15:34:04FromDiscord<Rika> what is bors?
15:34:14FromDiscord<enthus1ast> the mergebot?
15:34:39FromDiscord<enthus1ast> (had to google it myself)
15:34:56FromDiscord<enthus1ast> [Edit](https://discord.com/channels/371759389889003530/371759389889003532/904755219416637440): the mergebot maybe?
15:35:08FromDiscord<dom96> didn't know bors supported non-rs repos
15:35:20FromDiscord<leorize> it's not rocket science (literally \:p)\: https://graydon.livejournal.com/186550.html
15:35:23FromDiscord<dom96> I guess it's pretty configurable to run whatever you want
15:35:56FromDiscord<leorize> bors doesn't really care what repo you're using, it just waits on CI result
15:36:33FromDiscord<leorize> you can read the linked article to see the problem it solves
15:37:24FromDiscord<tandy> oh i thought bors was one of those bots that grabs commits from another repo mb
15:38:45FromDiscord<Rika> no thats called git pull xd
15:40:09NimEventerNew Nimble package! tecs - Simple ECS implementation for Nim, see https://github.com/Timofffee/tecs.nim
15:40:55FromDiscord<tandy> @Rika)
15:41:05FromDiscord<tandy> \_\>\:()
15:41:08FromDiscord<tandy> lol
15:41:27FromDiscord<Rika> what
15:46:12FromDiscord<leorize> I'm pretty sure that cps the library will continue to target Nim↡(@xflywind)
15:50:58FromDiscord<xflywind> Interesting; I see
16:00:00NimEventerNew thread by Archnim: Nim interpreter, see https://forum.nim-lang.org/t/8578
16:03:56FromDiscord<Yardanico> uh
16:04:33*neurocyte0132889 quit (Ping timeout: 268 seconds)
16:08:24*neurocyte0132889 joined #nim
16:08:24*neurocyte0132889 quit (Changing host)
16:08:24*neurocyte0132889 joined #nim
16:19:18FromDiscord<Rika> Lol
16:22:55*arkanoid joined #nim
16:23:18arkanoidhello! playing around with arraymancer for the first time. Do you know how to test if an element is contained in a tensor?
16:23:52arkanoidlike "7 in [0,1,2,3,4,5,6,7].toTensor" => true
16:33:14FromDiscord<Rika> does that not work directly?
16:34:01arkanoidno
16:34:30arkanoidRika: I have to 7 in myTensor.toSeq
16:36:01FromDiscord<Rika> seems like the proc doesnt exist indeed
16:36:46arkanoidI'm a champion in finding missing features on first use
16:56:06*neurocyte0132889 quit (Read error: Connection reset by peer)
16:56:37*neurocyte0132889 joined #nim
16:56:37*neurocyte0132889 quit (Changing host)
16:56:37*neurocyte0132889 joined #nim
17:14:12*rockcavera joined #nim
17:14:12*rockcavera quit (Changing host)
17:14:12*rockcavera joined #nim
17:30:59FromDiscord<geekrelief> In my nimble file, I'm trying to get the value of a `--cc` flag from `nim.cfg` using `get("cc")` https://nim-lang.org/docs/nimscript.html#get%2Cstring but it's returning empty. Any clue what I'm doing wrong?
17:37:20*rockcavera quit (Remote host closed the connection)
17:45:06FromDiscord<dom96> Nimble doesn't read nim.cfg
17:45:53FromDiscord<geekrelief> ok yeah, I guess I need to create a work around. I'm kind of confused. Is Nimble meant to be used as a build system?
17:46:33FromDiscord<geekrelief> I mean it kind of works, but it's a little awkward for me. Or maybe I just don't "get" it yet.
17:51:25FromDiscord<IsaacPaul> Still a good question.. how to know what compiler you're using inside of a cfg file.
17:51:49FromDiscord<IsaacPaul> (edit) "Still a good question.. how to know what compiler ... you're" added "(clang / gcc)"
17:58:40FromDiscord<IsaacPaul> Maybe just avoid the command flag --cc and use cc=clang inside if you config file.. I have a feeling the compiler flags are meant to override the configuration.
17:58:55FromDiscord<IsaacPaul> but idk
18:02:44FromDiscord<geekrelief> I'm sidestepping the issue for now. Using .cfg vs .nims has always been awkward for me. I thought with a new project I'd try using nimble as a build system, but maybe that's not its intent and I should look at nake?
18:04:59FromDiscord<Solitude> .cfg/nims are orthogonal to nimble
18:06:52FromDiscord<IsaacPaul> sent a code paste, see https://play.nim-lang.org/#ix=3DD3
18:08:03FromDiscord<IsaacPaul> to each .nim file
18:08:42FromDiscord<geekrelief> Yeah I'm using .cfg and .nims for setup, but I'm building multiple targets and I also need to switch compilers, so they need different flags too.
18:09:36FromDiscord<geekrelief> I building bindings which generate differently depending on the compiler, then I'm building a plugin against binding.
18:11:33FromDiscord<geekrelief> I want to define which compiler I'm using for the bindings and plugin in one place while allowing the bindings its own set of flags vs the plugin.
18:12:17FromDiscord<IsaacPaul> sent a code paste, see https://play.nim-lang.org/#ix=3DD5
18:12:41FromDiscord<IsaacPaul> then inside the if you know its clang or gcc or whatever
18:13:00FromDiscord<IsaacPaul> there's probably a better way
18:16:11FromDiscord<geekrelief> Yeah, that's probably going to be more convoluted than I'd like. It's so much easier to understand one file and set all the flags in there which is what I did for my prior project. Thanks for the suggestion though.
18:24:15FromDiscord<dom96> If you want a Nimble-only solution then you can do something like this: https://github.com/nim-lang/nimble/blob/master/tests/nimscript/nimscript.nimble#L34
18:28:32FromDiscord<haxscramper> does nimble even react to `--nimblePath`?
18:28:39FromDiscord<haxscramper> I'm trying to install package in non-default directory
18:28:53FromDiscord<haxscramper> `nimble install --nimblePath:(pwd) benchy`
18:29:35FromDiscord<haxscramper> same for `nimble --nimblePath:(pwd) install benchy`
18:30:01FromDiscord<Solitude> `--nimbleDir:dirname Set the Nimble directory.`
18:30:07FromDiscord<haxscramper> sht
18:30:12FromDiscord<haxscramper> 10^9 IQ time
18:35:01*neurocyte0132889 quit (Ping timeout: 268 seconds)
18:36:46FromDiscord<dom96> hm, Nimble should fatal with an invalid flag like that
18:36:56FromDiscord<dom96> I guess it doesn't?
18:38:17*neurocyte0132889 joined #nim
18:38:17*neurocyte0132889 quit (Changing host)
18:38:17*neurocyte0132889 joined #nim
18:42:20FromDiscord<Schelz> how to import a .cpp file in nim ?
18:47:08FromDiscord<haxscramper> no, it never failed with invalid flags↡(@dom96)
18:47:13FromDiscord<haxscramper> for as long as I can remember
18:47:29FromDiscord<hips> In reply to @Schelz "how to import a": perhaps https://github.com/nimterop/nimterop ?
18:47:43FromDiscord<haxscramper> if you want to try your luck yes,
18:48:00FromDiscord<haxscramper> Technically c2nim "supports" C++ as well, but I can't comment on how good this support is
18:48:24FromDiscord<haxscramper> Otherwise you can add read on the `importcpp` pragma on the manual and do wrapping by haand
18:50:17FromDiscord<Recruit_main707> pretty sure nimterop is abandoned and did not support c++ properly ever
18:50:38FromDiscord<Schelz> i can use c too its not a problem
18:50:55FromDiscord<haxscramper> my personal recommendation is to
18:51:04FromDiscord<haxscramper> well, how big/complex is the API?
18:51:53FromDiscord<Schelz> not pretty big some bool structure, and some int too
18:52:27FromDiscord<haxscramper> then I guess you can just try `c2nim api.h` and see how it goes
18:52:39FromDiscord<Schelz> isnt a solution to compile the cpp in .so and import it in nim ?
18:53:01FromDiscord<Schelz> like loading in it a dll and use it
18:53:03FromDiscord<haxscramper> it is a possibility, yes, but there are other ways
18:53:05FromDiscord<Recruit_main707> youd still need to wrap the functions
18:54:40FromDiscord<haxscramper> to work with dynamic libraries you can do `proc dynproc(arg: cint): SomeStructure {.importc: "nameOfTheProcInLibrary", dynlib.}`
18:55:15FromDiscord<haxscramper> And if you want to do using only headers you can wrap it as `proc headerproc(arg: cint): SomeStructure {.header: "header.h", importc: "nameOfTheProcInLibrary".}`
18:55:32FromDiscord<haxscramper> I suppose I forgot something in the `{..}`, but this is a general idea
19:02:18FromDiscord<IsaacPaul> Since it's a header file you'll better results by adding the `--header` flag when using c2nim.
19:03:15FromDiscord<haxscramper> it doesn't detect this based on file extension?
19:03:20FromDiscord<IsaacPaul> nope
19:06:58FromDiscord<IsaacPaul> weird .. maybe it does.. I remember initially having issues and now it seems to work
19:09:51FromDiscord<IsaacPaul> ah ok the difference is with `--header` c2nim will use importc and without it will try to just directly translate it to nim
19:10:06FromDiscord<IsaacPaul> so ya, nope
19:10:30arkanoidI'm trying to cross-compile from linux to windows for the first time using this config.nims: https://termbin.com/w1gg, but I'm getting "/usr/bin/x86_64-w64-mingw32-ld: cannot find -ldl"
19:16:42FromDiscord<Astavie> sent a code paste, see https://play.nim-lang.org/#ix=3DDu
19:17:59FromDiscord<Schelz> this is an error that give me when i compile a file that has glfw and imgui as dll and i run it https://media.discordapp.net/attachments/371759389889003532/904811526127489064/unknown.png
19:24:43arkanoidwhy -d:mingw works at command line, but fails with a config.nims with just that?
19:24:54FromDiscord<Schelz> dose anyone has libstdc++-6.dll.a in the mingw64 ?
19:24:59FromDiscord<Schelz> (edit) "dose anyone has libstdc++-6.dll.a in the mingw64 ... ?" added "floder"
19:25:04FromDiscord<Schelz> (edit) "floder" => "folder"
19:26:40arkanoidgot it: Note: In general, the define switches can also be set in NimScripts using switch or --, as shown in above examples. Few define switches such as -d:strip, -d:lto and -d:lto_incremental cannot be set in NimScripts.
19:26:51arkanoidhttps://nim-lang.org/docs/nims.html
19:31:34*krux02 joined #nim
19:32:52FromDiscord<dom96> In reply to @haxscramper "no, it never failed": we have such a long test suite for these flag behaviours, it's getting a bit nuts that there are still bugs
19:32:59FromDiscord<dom96> in any case, please submit a bug report
19:37:04*vicfred joined #nim
19:38:23FromDiscord<haxscramper> done
19:38:44NimEventerNew thread by Astavie: Did NRVO break?, see https://forum.nim-lang.org/t/8579
19:39:13FromDiscord<dom96> thanks!
19:41:34*fputs joined #nim
19:42:04*lucerne quit (Quit: Bye)
19:45:28*greyrat quit (Ping timeout: 252 seconds)
19:45:53*greyrat joined #nim
19:46:26*lucerne joined #nim
20:03:28FromDiscord<leorize> the same issue made -d\:release do nothing in config files (til recently)
21:08:59*fputs quit (Quit: The Lounge - https://thelounge.chat)
21:09:19*fputs joined #nim
21:53:13NimEventerNew thread by Giaco: Arraymancer `in` operator, see https://forum.nim-lang.org/t/8580
22:25:01*klil joined #nim
22:25:09klilwelcome
22:25:15klilhello
22:25:23klilcan you help me
22:25:26klilnim
22:26:27*klil quit (Client Quit)
22:39:46FromDiscord<dom96> don't ask to ask
22:39:50FromDiscord<dom96> just ask your question
22:55:16FromDiscord<sealmove> wtf: https://github.com/nim-works/nimskull
22:57:13arkanoidsealmove, exactly
22:57:28FromDiscord<sealmove> almost seems like a hoax
23:00:42arkanoidyou think?
23:01:58FromDiscord<sealmove> I don't understand >< help me
23:02:25arkanoidI can't
23:02:48FromDiscord<sealmove> Maybe he made it in April 1st?
23:03:18FromDiscord<leorize> it's a nim fork
23:03:39FromDiscord<leorize> that's all to it right now
23:04:04FromDiscord<sealmove> but I see a lot of big names contributing
23:04:15FromDiscord<sealmove> what's the rational?
23:04:54FromDiscord<leorize> we got tired of the way Nim is going
23:05:06FromDiscord<sealmove> which is?
23:05:20FromDiscord<sealmove> you mean the development process?
23:06:00FromDiscord<leorize> mostly, yeah
23:06:41FromDiscord<sealmove> sorry not trying to hit a vein here >< I'm truly ignorant, just saw the repo for the first time
23:06:54FromDiscord<leorize> don't worry \:p
23:07:26arkanoidis there a statement somewhere on the original nim channels about this? It's something the community should be aware of?
23:07:36FromDiscord<leorize> it's just been established and not a lot has happened yet
23:07:52FromDiscord<leorize> which is why it wasn't advertised, but somehow y'all caught on it \:p
23:08:10FromDiscord<Elegantbeef> We'll put the blame on me πŸ˜›
23:08:12FromDiscord<sealmove> github feed algorithm lol
23:08:18FromDiscord<sealmove> it's not just facebook or instagram
23:08:25FromDiscord<Elegantbeef> I'm just such a likeable person people follow me!
23:08:49FromDiscord<sealmove> actually it was disruptek for me, he starred it
23:09:08arkanoidI also got it from github feed
23:09:18FromDiscord<leorize> you can check the project tab for a roadmap
23:09:43FromDiscord<leorize> but functionally we haven't deviated yet
23:10:11FromDiscord<leorize> discussions is also open if y'all are interested in helping out
23:10:21FromDiscord<leorize> no chatroom yet, the thing is barely a week old
23:11:28arkanoidsure, thing, but the first topic would be what's the future of the community and general direction
23:13:25FromDiscord<leorize> [saem](https://matrix.to/#/@saem:matrix.org) should be the best person to provide a brief on this
23:14:02FromDiscord<leorize> afaict the direction right now is to fix the architecture of the compiler
23:14:08FromDiscord<Elegantbeef> My description would be a less tech debt filled compiler that enables "correct" code
23:15:38FromDiscord<leorize> what the project mean for the community would be a more robust compiler and a more streamlined process for getting stuff done
23:16:04FromDiscord<RattleyCooper> Having a good description will be important for people who don't know much about how nim works behind the curtain (totally not talking about me πŸ‘€)
23:16:15FromDiscord<leorize> with that said, consider the current state to be pre-pre-alpha \:p
23:16:26FromDiscord<leorize> more details will come on a later date
23:16:35FromDiscord<Elegantbeef> Yea we're more interested in contributors than a community \:d
23:17:34FromDiscord<RattleyCooper> In reply to @Elegantbeef "Yea we're more interested": Fine! 😒
23:17:34FromDiscord<leorize> currently we are driven by a few nim devs who work in their free time (on weekends only)
23:17:41FromDiscord<sealmove> So from what I understand after taking a better look, it looks like the compiler code was copied over and it's getting refactored to incorporate better testing.
23:18:24FromDiscord<Elegantbeef> Well that's the first step
23:18:25FromDiscord<leorize> yea, as I said, it's barely changed from mainline
23:18:42FromDiscord<Elegantbeef> It will change over time but right now it needs legs to stand on
23:20:13FromDiscord<sealmove> But it's 6-year old? And you sound like you came up with the idea yesterday
23:20:23FromDiscord<Elegantbeef> It's not 6 years old
23:20:30FromDiscord<Elegantbeef> It's a fork of the nim compiler
23:20:33FromDiscord<leorize> it's a week old lol
23:20:44FromDiscord<sealmove> ah ok x)
23:21:03FromDiscord<sealmove> I am stupid and forget how github forks work
23:21:07FromDiscord<Elegantbeef> We're not rebuilding from the ground up, we're modifying the already existent compiler
23:21:34FromDiscord<sealmove> Yes that's easy inferable looking at the repo
23:21:42FromDiscord<sealmove> (edit) "easy" => "easily"
23:22:02arkanoidis the plan to merge it later on?
23:22:27FromDiscord<Elegantbeef> Well we have changes that are incompatible with Nim so no
23:22:31FromDiscord<leorize> that's not planned right now
23:22:35FromDiscord<sealmove> <secretly doubt it :3>
23:22:50FromDiscord<Elegantbeef> I personally will try to port everything to both until i cannot
23:23:01FromDiscord<Elegantbeef> But at some point it's gotta be one or the other
23:23:12FromDiscord<leorize> one of the reason for the fork was that we disagree with the current development process after all \:p
23:23:41arkanoidk, got the idea. Well, I'm very happy to see experienced programmers willing to fork and improve. What scares me is that this could split the already small community
23:23:58FromDiscord<RattleyCooper> ngl I'm excited but also nervous bc I just "learned" nim lol. Guess it'll be a ways down the road.
23:24:12FromDiscord<Elegantbeef> Eh it's not going to change much in regards to syntax
23:24:22FromDiscord<Elegantbeef> New features will be added/some removed but the we love the syntax/language
23:24:31FromDiscord<leorize> having good tools has never break a language \:p
23:24:32FromDiscord<Elegantbeef> Or atleast intended language
23:25:17FromDiscord<RattleyCooper> Perfect. Yeah, that's what I love about nim as well so that's good to hear. Excited to see what happens. Can someone invite me to chat once it's up and running or I will a link be on the github page at some point?
23:25:30FromDiscord<RattleyCooper> (edit) removed "I"
23:25:46FromDiscord<Elegantbeef> There will be a link eventually, when it's sufficiently progressed
23:25:52FromDiscord<RattleyCooper> Cool cool!
23:26:13FromDiscord<Elegantbeef> Presently we're more interested in people contributing than growing a community, so if you want to see it sooner, get on helping hax with language spec tests
23:27:05FromDiscord<sealmove> "spec testing"... looks like just more tests :P
23:27:06FromDiscord<Elegantbeef> It's a relatively simple thing anyone should be able to handle, chip away at a few tests and make a PR
23:27:23FromDiscord<Elegantbeef> It's establishing the language through tests instead of words
23:28:45FromDiscord<Elegantbeef> In saem's words you should be able to learn the language from reading the spec tests
23:29:08FromDiscord<sealmove> That's a curious idea, never heard of something similar
23:29:17FromDiscord<leorize> and most importantly it will be the basis for some of the large refactoring planned
23:29:54FromDiscord<Elegantbeef> Yep, plus feature additions can be written in the test spec and used to test it workiing
23:30:10FromDiscord<tandy> i saw hc's issue/pr this is a great plan
23:30:20FromDiscord<tandy> how will this be done?
23:30:48arkanoidapart from making the language more testable, which breaking improvements are you willing to add at the end of the refactoring?
23:31:02FromDiscord<leorize> nkError is the first step, of which you can see the pipeline in the projects tab
23:31:03FromDiscord<tandy> at the moment you learn nim by seeing it / being involved etc but having this kind of document would be invaluable
23:31:16FromDiscord<tandy> also means less time writing documentation!
23:31:54FromDiscord<tandy> would this feature be mergeable into nim?
23:31:56FromDiscord<Elegantbeef> We have some language changes for bad for human parts of nim (Distincts/hooks)
23:32:04FromDiscord<tandy> has there been any communication with nim dev team?
23:32:13FromDiscord<sealmove> Can it really replace documentation? Some concepts can't be explained through code
23:32:19FromDiscord<leorize> but, uh remember that this is a week old and we work on weekends only
23:32:32FromDiscord<Elegantbeef> Some of us only work on weekends πŸ˜›
23:32:38FromDiscord<Elegantbeef> Some of use dont even work on it
23:32:40FromDiscord<tandy> i think for a lot of things it can help, which is where nim is lacking on documentation atm↡(@sealmove)
23:32:42FromDiscord<Elegantbeef> [Edit](https://discord.com/channels/371759389889003530/371759389889003532/904875612479565895): Some of us dont even work on it
23:32:58FromDiscord<Elegantbeef> I mean it's not just tests, there are also comments included with the tests
23:33:02FromDiscord<tandy> if i wasnt a student id send u guys money lol
23:33:04FromDiscord<Elegantbeef> So you have words + code
23:33:45FromDiscord<leorize> replacing docs is not the final goal of the spec tests, mind you \:p
23:33:46FromDiscord<Elegantbeef> Donations accepted include adding tests πŸ˜›
23:34:04FromDiscord<leorize> the major refactorings will break things and we need extra tests to cover ourselves
23:34:26FromDiscord<tandy> il start contributing when i finish in 6 months
23:34:28FromDiscord<tandy> \:))
23:34:45FromDiscord<tandy> its defo a nice bonus tho \:)
23:35:22FromDiscord<tandy> one slightly irelevant thing, is infrastructure available to measure regressions through CI?
23:35:44FromDiscord<tandy> like i know benchmarking with ci is bad but maybe it could be useful for this kind of scale ..
23:36:31FromDiscord<leorize> not yet
23:37:01FromDiscord<leorize> there might be something, but I can't promise that
23:37:46FromDiscord<tandy> i was more talking in general, about whether some solution existed
23:37:51FromDiscord<tandy> would b nice to have
23:38:53FromDiscord<leorize> maybe in the very far future we will get a server rack to run benchmark on
23:39:08FromDiscord<leorize> but, again, this thing is a week old so please wait \:p
23:39:47arkanoidare you expecting a discussion with araq and other core devs?
23:40:22FromDiscord<tandy> yes, haha
23:41:21arkanoidsplitting nim won't help people like me trying to push nim into production
23:42:03FromDiscord<tandy> tell that to the core team↡(<@709044657232936960_arkanoid=5b=49=52=43=5d>)
23:42:19FromDiscord<tandy> not these guys who are putting effort into making nim a community effort
23:44:37FromDiscord<sealmove> This will help LSP?
23:45:00FromDiscord<sealmove> If so it's the main selling point imo
23:45:26FromDiscord<sealmove> <leorize feeling the pressure :>>
23:45:59FromDiscord<leorize> I'm alternating between cooking and chatting \:p
23:46:24FromDiscord<leorize> and it doesn't help that y'all are asking a lot out of the week old project \:p
23:47:28FromDiscord<sealmove> you can't be this insurrectional and expect no questions
23:47:50FromDiscord<leorize> I'd say that more info will come as more work is put in
23:48:11FromDiscord<leorize> there isn't much that I can say right now, the project has more than just me \:p
23:48:42FromDiscord<sealmove> I am almost persuaded to help :3
23:50:11FromDiscord<sealmove> rn as far as nim is concerned, i would like to contribute to anything that bring us closer to having advanced ide tooling
23:50:29arkanoidagree
23:52:11FromDiscord<sealmove> I suspect key tooling components are hard to build right now because the compiler is not modular enough rn, but I could be completely wrong since I don't understand much of the compiler code.
23:57:42FromDiscord<evoalg> So the aim isn't just for a different compiler, but a new language? Similar but different? So tutorials / books will be written eventually?
23:58:27*brain-soup joined #nim
23:59:08FromDiscord<sealmove> No it's the same language