<< 02-04-2026 >>

01:22:47*syl_ is now known as syl
02:29:07*rockcavera quit (Remote host closed the connection)
03:28:40FromDiscord<janakali> @TӨMΛ ☠ https://play.nim-lang.org/#pasty=UQBGmGvy
03:37:38*xet7 quit (Remote host closed the connection)
04:56:01*mrinsane_ joined #nim
04:57:02*mrinsane quit (Ping timeout: 268 seconds)
06:51:22*hygo quit (Quit: WeeChat 4.7.1)
06:53:33*hygo joined #nim
07:50:26*SchweinDeBurg quit (Quit: WeeChat 4.8.0-dev)
07:55:27*SchweinDeBurg joined #nim
08:35:57*mrinsane_ quit (Ping timeout: 268 seconds)
08:58:07FromDiscord<[Next-System] systemblue> is there anyone whoknow cheatful's discord ID↵who made Nim-Crypto?
09:15:53FromDiscord<[Next-System] systemblue> sent a code paste, see https://play.nim-lang.org/#pasty=IZgTrNie
09:16:20FromDiscord<[Next-System] systemblue> I think it should be warned and deprecated
09:17:18FromDiscord<janakali> you can search it on discord. iirc he uses same username as on github
09:20:01FromDiscord<[Next-System] systemblue> @cheatfate
09:20:02FromDiscord<[Next-System] systemblue> right?
09:20:30FromDiscord<[Next-System] systemblue> In reply to @janakali "you can search it": you have just moved to matrix right?↵why?
09:32:47FromDiscord<ieltan> In reply to @bluewhale_unkown_x "there are plenty of": my advice: make a PR on the original repo but dont wait too long if you dont get an answer, fork and make a post on the forum about it
09:47:20FromDiscord<[Next-System] systemblue> yes I'm trying to fix it and making other library
09:51:23FromDiscord<cheatfate> agree that twofish implementation is vulnerable to timing attack, because implementation is pretty old and based on old implementation too (when nobody even care about timing attacks
09:51:29FromDiscord<cheatfate> (edit) "attacks" => "attacks)"
10:34:27*xet7 joined #nim
13:12:18FromDiscord<janakali> sent a long message, see https://pasty.ee/wvNxnqpN
13:17:46Amun-Rano cli client is a no go for me
13:33:55FromDiscord<litlighilit> matrix↵(<@709044657232936960_=41mun-=52a=5b=49=52=43=5d>)
13:34:51FromDiscord<litlighilit> here're several matrix tui.↵and this matrix room us equiped with discord bridge
13:35:03FromDiscord<litlighilit> here're several matrix tui.↵and this matrix room is equiped with discord bridge
13:55:45Amun-Raare all nim discords rooms visible on matrix?
14:23:19FromDiscord<olfactoryhallucinations> No, there are some some that are missing, like #nimony , #langdev and the language specific ones.
14:23:43FromDiscord<olfactoryhallucinations> At least I can't see them.
14:30:39*mrinsane joined #nim
17:03:52FromDiscord<leeeee2976> does anybody know how to disable garbage collection on Nimony?
17:24:05FromDiscord<leeeee2976> Oh I found it, nvm. So Nimony doesn't have --mm switch
17:47:55FromDiscord<jabuci> sent a code paste, see https://play.nim-lang.org/#pasty=mAdTqFMI
18:27:46FromDiscord<nasuray> In reply to @jabuci "I have this code:": https://nim-lang.org/docs/manual.html#lexical-analysis-triple-quoted-string-literals this is just how triple quote string literals work in nim
18:36:33FromDiscord<nervecenter> In reply to @jabuci "I have this code:": There's no "should" or "shouldn't" there. Triple quoted strings in Nim don't include a leading newline if you line-seperate the quotes and text. Nim is under no obligation to behave like Python.
18:37:31FromDiscord<nervecenter> Also Nim does not distinguish between byte strings and text strings, so that should tell you that they're different right away.
18:42:52FromDiscord<jabuci> OK, thanks.
19:10:03FromDiscord<nnsee> while it's true that this is documented and just part of the syntax which is fine, i also think it's counterintuitive and don't understand the point of it
20:19:40om3ganervecenter: byte == char
21:46:38FromDiscord<nervecenter> In reply to @om3ga "<@143177514385145856>: byte == char": Fundamentally, yes. Standard library-wise, no. Files and pipes operate on and return `string`. Araq has said as much, that he prefers `string` to work as dual-function and that `seq[byte]` is an anti-pattern.
21:47:00FromDiscord<nervecenter> (edit) "work as" => "operate with"
21:47:17FromDiscord<nervecenter> (edit) "is an anti-pattern." => "and `seq[char]` are anti-patterns."
21:56:11om3ganervecenter: I don't understand what benefits it will give or will change. All platforms except couple dsp's have 8 bit char and byte
22:00:17FromDiscord<nervecenter> In reply to @om3ga "<@143177514385145856>: I don't understand": `string` elements are technically `char` when indexed, so they are also 8 bits
22:02:01om3ganervecenter: so it means no indexing will apply on seq[byte]?
22:27:26FromDiscord<nervecenter> In reply to @om3ga "<@143177514385145856>: so it means": You'd have to explicitly convert indexed `byte` elements to `char`
22:27:36FromDiscord<nervecenter> Depending on the use
22:41:14om3gainteresting
23:28:56FromDiscord<janakali> it's useful when you need to align text verticallyin python people often use `str = """\` to skip first line. This is ugly and doesn't work in nim. Implicit newline IMO is better solution.what's intersting, the similar feature was proposed to python, but even more extreme, with automatic dedent\: https://peps.python.org/pep-0295/↵(@nnsee)
23:40:09FromDiscord<tsoj> how do i get nimble on aarch64?
23:41:07FromDiscord<tsoj> the released binaries for aarch64 seem to be x86
23:41:11FromDiscord<tsoj> (edit) "x86" => "x86-64"
23:41:51FromDiscord<tsoj> and building it from source runs into an hen egg problem