<< 03-04-2026 >>

00:07:15FromDiscord<demotomohiro> In reply to @tsoj "how do i get": If you build from source and have GCC, git clone https://github.com/nim-lang/Nim and run `build_all.sh`.↵Then, nimble should be in `bin` directory.
00:09:01FromDiscord<demotomohiro> Or download source from: https://nim-lang.org/install_unix.html
00:09:15FromDiscord<tsoj> ahh thanks, I managed to use AI to fix it already (i think) ;) <https://github.com/tsoj/nimble/actions/runs/23927449413/job/69787183445>
00:12:25FromDiscord<tsoj> or maybe not nvm
01:18:36FromDiscord<janakali> @tsojnightly releases are built correctly for arm64\: https://github.com/nim-lang/nightlies/releases↵you can extract it and get nimble from "/bin"
01:19:29FromDiscord<janakali> @tsojnightly releases are built correctly for arm64\: https://github.com/nim-lang/nightlies/releases↵you can extract archive and get nimble from "/bin"
01:23:13FromDiscord<nasuray> In reply to @tsoj "the released binaries for": please submit an issue for `nim-lang/nimble` about that (if it doesn't already exist that is)
01:27:49*tk quit (Ping timeout: 245 seconds)
01:30:24*tk joined #nim
02:20:13*deavmi quit (Quit: No Ping reply in 180 seconds.)
02:31:09*deavmi joined #nim
05:04:39*alexdaguy joined #nim
05:11:36*levovix joined #nim
05:11:53*alexdaguy quit (Quit: re)
05:12:02*levovix quit (Client Quit)
05:44:08*mrinsane quit (Ping timeout: 256 seconds)
06:22:08FromDiscord<nnsee> In reply to @janakali "it's useful when you": i've written a loooot of python and never been in a situation where a leading newline is an issue. in general, if you're including such multiline strings in code to begin with that are long enough that you have to consider the implications of the leading newline or even dedenting, you're doing something wrong. also i don't think i've ever seen someone use `"""\`
06:23:13FromDiscord<nnsee> also that pep was rejected
06:23:20FromDiscord<nnsee> for pretty good reasons, i think
06:49:18FromDiscord<litlighilit> if u get used to Nim's, you'll find Python's uncomfortable
06:50:11FromDiscord<litlighilit> as often a leading newline was not expected
06:51:50FromDiscord<litlighilit> but without one the code seems weird, especially the line of the string literal is indented
06:53:04FromDiscord<litlighilit> but without one the code seems weird, especially when the line of the string literal is indented
06:53:27FromDiscord<janakali> sent a long message, see https://pasty.ee/VCWwgbww
06:54:18FromDiscord<litlighilit> also, another difference between Nim and Python's multiline string literal is that
06:54:44FromDiscord<nnsee> In reply to @janakali "> "\>i don't think": i don't think this proves what you think it proves. 500k on github for such a popular language as python is practically nothing
06:54:46FromDiscord<litlighilit> Nim's doesn't interpret escape char like \`\\n\`
06:57:24FromDiscord<litlighilit> sent a long message, see https://pasty.ee/iYpguXLo
06:58:26FromDiscord<litlighilit> sent a code paste, see https://play.nim-lang.org/#pasty=IlpbweWM
06:58:38FromDiscord<nnsee> in any case, i think being explicit about it like python instead of having a surprising "hidden" behavior like nim is the better option here
06:59:20FromDiscord<litlighilit> what it comes to surprise, isn't C++'s R-string more?
06:59:39FromDiscord<nnsee> if i start a multiline string, and the first character in the string is a newline, i don't expect my newline to get eaten silently. that's surprising behavior that's not intuitive or in line with the rest of the syntax and requires you to read the language definition to understand
07:00:30FromDiscord<litlighilit> I think you can just write such a Nim code and then you'll get it
07:01:40FromDiscord<litlighilit> for this opinion I'd say u a right, tho C++'s R-string is even hard to understand even after you read lang specification↵(@nnsee)
07:04:06FromDiscord<litlighilit> sent a code paste, see https://play.nim-lang.org/#pasty=VOxMrneX
07:04:15FromDiscord<janakali> I can put it the other way. There's 2.3M hits for `/=\s+"""\n/` and 240K hits for `/=\s+"""\\\n/`, so roughly 10%↵(@nnsee)
07:04:45FromDiscord<janakali> which is not insignificant
07:10:27FromDiscord<litlighilit> sent a long message, see https://pasty.ee/ZwOPJYZr
07:12:50FromDiscord<litlighilit> and it's also true that Nim lacks some features of Python's, where nimpylib tries to provide
07:56:34*SchweinDeBurg quit (Quit: WeeChat 4.8.0-dev)
08:04:54*SchweinDeBurg joined #nim
08:51:06FromDiscord<litlighilit> How to declare test-only dep in .nimble?↵like Rust cargo.toml \`[test]\` section
09:25:05FromDiscord<nnsee> In reply to @litlighilit "<@961485620075720734>  btw I myself am": i'm familiar with nimpylib, it's a good library :)
09:28:41FromDiscord<nnsee> sent a long message, see https://pasty.ee/ZZlRuMke
11:03:32FromDiscord<janakali> @litlighilit put under "dev" feature section in .nimble https://nim-lang.github.io/nimble/create-packages.html#the-dev-feature
11:04:15FromDiscord<janakali> @litlighilit put it under `feature "dev":` section in .nimble https://nim-lang.github.io/nimble/create-packages.html#the-dev-feature
13:47:53*shrikant joined #nim
14:10:19FromDiscord<litlighilit> So was what i said, but older nimble lacks this.
14:11:11FromDiscord<litlighilit> So was what i knew, but older nimble lacks this.
15:54:26*shrikant quit (Ping timeout: 256 seconds)
16:50:20*mrinsane joined #nim
18:08:02FromDiscord<requiresupport> anyone setup nim lsp with opennode? 🤔
18:44:47*Mister_Magister_ joined #nim
18:45:55*Mister_Magister quit (Ping timeout: 264 seconds)
18:48:04*Mister_Magister_ is now known as Mister_Magister
19:38:35*xet7 quit (Remote host closed the connection)
19:42:13*xet7 joined #nim
20:06:29*xet7 quit (Quit: Leaving)
20:07:33*xet7 joined #nim