<< 13-06-2026 >>
00:06:22*shanoaice quit (Quit: The Lounge - https://thelounge.chat)
00:06:57*shanoaice joined #nim
01:14:11*Jjp137 quit (Quit: Leaving)
01:20:50*xet7 quit (Ping timeout: 248 seconds)
01:23:20*Jjp137 joined #nim
01:33:09*xet7 joined #nim
03:07:25*SandyUser joined #nim
03:07:53*SandyUser quit (Remote host closed the connection)
04:10:29*rockcavera joined #nim
04:35:23FromDiscord<mratsim> In reply to @demotomohiro "https://en.wikipedia.org/wiki/Universal_quantificat": that's a fun rabbithole
04:39:40FromDiscord<mratsim> sent a long message, see https://pasty.ee/lzGCxXfP
04:39:58FromDiscord<mratsim> (edit) "https://pasty.ee/SkGVXhPp" => "https://pasty.ee/BsoJYiDj"
04:41:26FromDiscord<tar> i like https://chawan.net
07:01:52*tiorock joined #nim
07:01:53*tiorock quit (Changing host)
07:01:53*tiorock joined #nim
07:01:53*rockcavera is now known as Guest7035
07:01:53*Guest7035 quit (Killed (copper.libera.chat (Nickname regained by services)))
07:01:53*tiorock is now known as rockcavera
08:38:42*Skippy8 joined #nim
08:41:16FromDiscord<declasy> In reply to @mratsim "I use it for:": is it hard?
08:42:37FromDiscord<grotesquemalfeasance> yes
08:42:53FromDiscord<grotesquemalfeasance> ive actually had a lot less trouble with nim than c++ though, funnily enoug
08:43:29FromDiscord<grotesquemalfeasance> its just that there isnt a overabundance of guides and resources, so you kind of have to figure out things yourself, which i kind of prefer
08:44:03FromDiscord<declasy> ok but can nim compile to exe?
08:44:09FromDiscord<grotesquemalfeasance> yes
08:44:16FromDiscord<grotesquemalfeasance> it cross compiles to c
08:44:26FromDiscord<grotesquemalfeasance> anything you can do with c you can do with nim basically
08:45:07FromDiscord<declasy> In reply to @grotesquemalfeasance "anything you can do": how come?
08:45:26FromDiscord<grotesquemalfeasance> it runs anywhere c runs, and you get all the performance optimizations of c for free
08:46:45FromDiscord<declasy> In reply to @grotesquemalfeasance "it runs anywhere c": how is the learning curve compared to golang?
08:49:52FromDiscord<grotesquemalfeasance> probably about the same
08:51:40FromDiscord<grotesquemalfeasance> they're both primarily used by people already proficient in other languages
09:10:11FromDiscord<declasy> In reply to @grotesquemalfeasance "they're both primarily used": I'm a noobie golang adept
10:26:58FromDiscord<tauruuuuuus> Golang is much easier imho if you consider the full extent of the nim language and features
10:27:07FromDiscord<tauruuuuuus> But nim is more powerful and expressive imho
10:40:47*Skippy8 quit (Read error: Connection reset by peer)
10:41:44*Skippy8 joined #nim
12:20:06FromDiscord<mratsim> In reply to @declasy "how come?": you run c2nim on any code in C and it's converted to NIm. No LLM was hurt in the process
12:20:15FromDiscord<mratsim> someone did thatwith Quake
12:20:25FromDiscord<mratsim> (edit) "thatwith" => "that with"
12:20:30FromDiscord<declasy> ok
12:21:07FromDiscord<mratsim> In reply to @declasy "is it hard?": hard as in?
12:22:21FromDiscord<tempestro> just try and take it out for a spin
12:25:08FromDiscord<mratsim> In reply to @declasy "is it hard?": I started developing in Nim, it's basically the first lang I developed for more than say 48 hours projects with
12:31:07*acidsys quit (Ping timeout: 244 seconds)
12:38:36*beholders_eye joined #nim
12:39:47*Skippy8 quit (Read error: Connection reset by peer)
12:40:26*Skippy8 joined #nim
12:53:06*acidsys joined #nim
14:15:46FromDiscord<shalokshalom> In reply to @declasy "how is the learning": Its a bit more difficult, and also more powerful. Go is simple, and Nim can be simple, but has more language features, and can mess up more. Ask often here for a short code review, and you are fine.↵↵Nim rewards you with a more flexible coding style, more control over the performance and direct C compatability.
14:16:34FromDiscord<declasy> In reply to @shalokshalom "Its a bit more": Can I make my own language with Nim?
14:16:43FromDiscord<shalokshalom> I recommend that you use Nim very similar to how you use Go: That's generally a good idea: ↵↵Start simple, and when you need it, reach for the more advanced features.
14:17:00FromDiscord<shalokshalom> In reply to @declasy "Can I make my": Yes, there is even a dedicated channel for it: ↵#langdev
14:17:12FromDiscord<declasy> In reply to @shalokshalom "I recommend that you": ok
14:19:00FromDiscord<declasy> In reply to @shalokshalom "Yes, there is even": Can you be my mentor plz?
14:20:50FromDiscord<blockyboy.> Hey
14:20:58FromDiscord<blockyboy.> (edit) "Hey" => "Hello guys"
14:21:11FromDiscord<blockyboy.> Im a bit new to learning Nim(coming from Java)
14:21:36FromDiscord<blockyboy.> Im wondering what are some mistakes i should avoid early on using nim
14:24:14*amadaluzia quit (Read error: Connection reset by peer)
14:25:06*amadaluzia joined #nim
14:27:55FromDiscord<declasy> In reply to @blockyboy. "Im wondering what are": https://media.discordapp.net/attachments/371759389889003532/1515362081157939341/message.txt?ex=6a2eba6a&is=6a2d68ea&hm=ebf9f056db1c2b1fd90ef001b7d2915051d14a029b83c5aeede1858d47c999f1&
14:31:55FromDiscord<blockyboy.> In reply to @declasy "": Nim's style sensitivity seems like a surprise that I haven't run into yet haha. Other than that thanks!
14:32:13FromDiscord<declasy> In reply to @blockyboy. "Nim's style sensitivity seems": yw
14:40:35*Skippy8 quit (Read error: Connection reset by peer)
14:43:02*Skippy8 joined #nim
14:43:47FromDiscord<20milliliter> sent a long message, see https://pasty.ee/yOymQbij
14:43:51FromDiscord<shalokshalom> In reply to @declasy "Can you be my": I barely know Nim from a practical standpoint, so I am not a good tutor. But I recommend you to build something small, that you can easily build, and collect some experience from there. 🙂
14:44:20FromDiscord<declasy> In reply to @shalokshalom "I barely know Nim": I'll language hopp again I guess...
14:45:11FromDiscord<shalokshalom> What are you looking for?
14:45:14FromDiscord<shalokshalom> #offtopic
14:47:31*Skippy8 quit (Ping timeout: 265 seconds)
14:48:01*Skippy8 joined #nim
15:49:23*Skippy8 quit (Ping timeout: 252 seconds)
15:49:39FromDiscord<alipolo17777> whats the naming convention for nim module names?↵no capital letter or underscore ?
15:50:04FromDiscord<alipolo17777> standard library module names seems to follow this convention and ngl it makes reading the names a bit harder
15:51:38*Skippy8 joined #nim
16:22:37FromDiscord<nasuray> Underscores and capitals are allowed but conventionally they are lowercase (possibly elucidated in the style guide)
16:23:56FromDiscord<alipolo17777> In reply to @nasuray "Underscores and capitals are": standard library style guide makes no mention of module name
16:26:32FromDiscord<nasuray> In reply to @alipolo17777 "standard library style guide": Ah than do whatever you want that compiler will let you lol
16:26:56FromDiscord<Laylie> all lowercase no underscores in module names please
16:27:11FromDiscord<Laylie> if this is insufficient the module name is too long
16:29:10FromDiscord<alipolo17777> In reply to @Laylie "all lowercase no underscores": doesnt that hurt readability ?↵i think nim is the only language that does that for module names
16:30:45*amadaluzia quit (Read error: Connection reset by peer)
16:31:14*amadaluzia joined #nim
16:31:56*amadaluzia quit (Read error: Connection reset by peer)
16:34:33FromDiscord<20milliliter> In reply to @Laylie "all lowercase no underscores": Unless I'm misunderstanding [this](<https://nim-lang.org/docs/manual.html#lexical-analysis-identifier-equality>) underscores are stripped from identifiers? So no, they are perfectly fine?
16:35:13FromDiscord<20milliliter> In reply to @nasuray "Ah than do whatever": And what "the compiler will let you" (again, iiuc) appears to be [here](<https://nim-lang.org/docs/manual.html#lexical-analysis-identifiers-amp-keywords>)
16:35:45FromDiscord<20milliliter> (edit) "[this](<https://nim-lang.org/docs/manual.html#lexical-analysis-identifier-equality>)" => "[this](<https://nim-lang.org/docs/manual.html#lexical-analysis-identifier-equality>),"
16:36:10FromDiscord<Laylie> i think the question was what the convention is, not what the compiler allows
16:36:14*amadaluzia joined #nim
16:37:25FromDiscord<20milliliter> fair
16:39:59*beholders_eye quit (Ping timeout: 252 seconds)
16:44:12*Skippy8 quit (Ping timeout: 246 seconds)
16:44:23FromDiscord<nasuray> In reply to @Laylie "all lowercase no underscores": Plenty of folks already use underscores including in package names.
16:44:59*Skippy8 joined #nim
16:45:37FromDiscord<Laylie> no doubt
16:45:41FromDiscord<Laylie> i am advocating the position that they shouldn't
16:45:45FromDiscord<_timurski> why
16:45:53FromDiscord<_timurski> I use snake case and pascal case exclusively
16:45:56FromDiscord<_timurski> pascal for type names
16:46:01FromDiscord<_timurski> snake case for everything elde
16:46:04FromDiscord<_timurski> (edit) "elde" => "else"
16:46:41FromDiscord<_timurski> I understand the appeal of using different cases for different objects to differentiate them but for my personal preference, the readibility benefits of snake case are just too great
16:47:45FromDiscord<_timurski> + other cases become ambiguous with names that might have capital letters in them as is common with camel case for example
16:47:53FromDiscord<_timurski> snake case has this problem much less often
16:50:23FromDiscord<_timurski> to be honest though my ideal naming convention is to use mathematical symbols for much of my code as that's its context, and eventually I'll write my own code editor which allows rendering this properly, as I don't think terminals can do it well..