<< 25-04-2026 >>
00:07:53*Guest44 joined #nim
00:11:00FromDiscord<janakali> @righthandofdoom next version after 2.2 is going to be 2.4 (odd versions are "in development"), but there's not very much planned as I can see\:↵https://github.com/nim-lang/RFCs/issues/556
00:11:29FromDiscord<janakali> most work right now is done on Nimony and fixing Nim 2.2 bugs
00:12:34*Guest44 quit (Client Quit)
00:22:54FromDiscord<righthandofdoom> In reply to @janakali "<@356024712498774027> next version after": is nimony going to be vastly different from current one? language not the compiler
00:33:05FromDiscord<planetis_m> In reply to @righthandofdoom "is nimony going to": https://github.com/nim-lang/nimony/blob/master/doc/differences.md there're quite some differences, but there's also compatibility with nimv2 via the feature pragma
00:43:42FromDiscord<righthandofdoom> In reply to @planetis_m "https://github.com/nim-lang/nimony/blob/master/doc/": wanna try effect system
00:43:50FromDiscord<righthandofdoom> is nimomy useful yet
00:47:29FromDiscord<righthandofdoom> araq is a machine
00:50:45*deavmi quit (Read error: Connection reset by peer)
00:59:46*deavmi joined #nim
01:00:46FromDiscord<planetis_m> the effect system exists only in nimv2
01:23:51FromDiscord<planetis_m> Is nimony useful? Try it and you be the judge.
01:45:19*rockcavera joined #nim
02:53:28*ephapticpulse left #nim (ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.3))
07:01:17*tiorock joined #nim
07:01:17*tiorock quit (Changing host)
07:01:17*tiorock joined #nim
07:01:17*rockcavera quit (Killed (uranium.libera.chat (Nickname regained by services)))
07:01:17*tiorock is now known as rockcavera
07:23:09*Freneticks quit (Ping timeout: 246 seconds)
07:25:38*robertmeta quit (Ping timeout: 248 seconds)
07:25:51*Freneticks joined #nim
07:29:07*robertmeta joined #nim
07:36:04*Freneticks quit (Ping timeout: 244 seconds)
07:36:48*Freneticks joined #nim
07:41:24*PMunch_ joined #nim
07:42:41*casaca quit (Ping timeout: 244 seconds)
07:43:45*casaca joined #nim
07:44:09*PMunch quit (Ping timeout: 246 seconds)
07:53:11FromDiscord<[Next-System] systemblue> In reply to @planetis_m "the effect system exists": it means, effect system are removed in nimv3 (nimomy)?
07:53:22FromDiscord<[Next-System] systemblue> (edit) "are" => "is"
07:53:31FromDiscord<[Next-System] systemblue> (edit) "is" => "will be"
07:53:39FromDiscord<[Next-System] systemblue> In reply to @narimiran "## Nim 2.2.10 is": really?
07:54:28FromDiscord<[Next-System] systemblue> do you think Nim is good name?↵when I search about nim in internet
07:54:38FromDiscord<[Next-System] systemblue> most result are about NVIDIA Nim and Nim game
07:54:51FromDiscord<[Next-System] systemblue> Nim debugging -> it's all about NVIDIA Nim
07:55:22FromDiscord<[Next-System] systemblue> I think our name are not good ↵↵I'm carefully asking your opinion about our names
07:55:42FromDiscord<[Next-System] systemblue> (edit) "are" => "is"
07:56:00FromDiscord<[Next-System] systemblue> nimble looks good
07:56:06FromDiscord<[Next-System] systemblue> but nim doesn't
08:21:00FromDiscord<planetis_m> In reply to @bluewhale_unkown_x "it means, effect system": It's not implemented yet AFAIK
08:27:10*Guest25 joined #nim
08:27:52*Guest25 quit (Client Quit)
08:37:44FromDiscord<[Next-System] systemblue> is there any plan for nim native backend?
08:37:49FromDiscord<[Next-System] systemblue> I heard about FASM native backend
08:37:54FromDiscord<[Next-System] systemblue> from araq
08:57:03FromDiscord<planetis_m> dunno, I am not part of the dev team
09:16:17*skippy8 joined #nim
09:22:35*PMunch joined #nim
09:25:38*PMunch_ quit (Ping timeout: 248 seconds)
09:59:09*PMunch_ joined #nim
10:02:55*PMunch quit (Ping timeout: 276 seconds)
10:23:40*rockcavera quit (Remote host closed the connection)
10:56:06FromDiscord<nnsee> In reply to @bluewhale_unkown_x "most result are about": Nim, the language, existed far before those did
10:56:33FromDiscord<nnsee> also it used to be called Nimrod
10:56:50FromDiscord<[Next-System] systemblue> In reply to @nnsee "Nim, the language, existed": ?? Nim game existed more than nim
10:57:06FromDiscord<[Next-System] systemblue> and NVIDIA Nim is much popular than nim... QQ
10:58:33FromDiscord<nnsee> oh you mean that nim
10:59:11FromDiscord<nnsee> it's not really in the same domain as Nim, the programming language, so it's not really an issue or source of confusion unlike nvidia's nim
11:00:01FromDiscord<nnsee> In reply to @bluewhale_unkown_x "and NVIDIA Nim is": there's only so many things you can name a project. if it has a short name, it's bound to collide with something else. you can't (and there's really no point to) escape that
11:18:47*PMunch joined #nim
11:21:45*PMunch_ quit (Ping timeout: 255 seconds)
13:46:06*rockcavera joined #nim
14:06:20*beholders_eye joined #nim
14:09:27*deavmi quit (Read error: Connection reset by peer)
14:10:44*beholders_eye quit (Ping timeout: 245 seconds)
14:14:02*deavmi joined #nim
14:23:30*deavmi quit (Quit: Eish, load shedding!)
14:32:40*deavmi joined #nim
16:25:50*xet7 quit (Remote host closed the connection)
17:05:51*xet7 joined #nim
17:27:30*rockcavera quit (Remote host closed the connection)
18:01:47*gabreal joined #nim
18:16:13*townscap_ joined #nim
18:25:16*xet7 quit (Quit: Leaving)
18:37:15*townscap_ is now known as townscaper
19:31:38*xet7 joined #nim
19:39:59*townscaper quit ()
21:05:35*ephapticpulse joined #nim
21:29:51FromDiscord<spotlightkid> Why do `-d:lto` and `-d:strip` work only the command line but not in `nim.cfg` or `config.nims` (`switch("define", "lto")` etc.)?↵Is it because `$nim/config/nim.cfg` is provcessed before `./nim.cfg` / `./config.nims`?↵https://github.com/nim-lang/Nim/blob/devel/config/nim.cfg#L330↵Was it always this way?
23:14:20*ftajhii joined #nim
23:17:34*ftajhii quit (Client Quit)
23:22:58*ftajhii joined #nim
23:35:18*skippy8 left #nim (WeeChat 4.8.1)
23:44:08*PMunch_ joined #nim
23:46:59*PMunch quit (Ping timeout: 245 seconds)