<< 14-12-2025 >>
00:58:50FromDiscord<bluewhale_unkown_x> may I ask you some question?
00:59:52FromDiscord<bluewhale_unkown_x> in Nim, ↵↵`arr[0..3]` is it same with↵openArray?
01:01:26FromDiscord<bluewhale_unkown_x> sent a code paste, see https://play.nim-lang.org/#pasty=JSBhlBJw
01:11:29FromDiscord<aethrvmn> `openArray` means that the template can now accept both `array` and `seq`↵(@bluewhale_unkown_x)
01:15:29*ftajhii quit (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
01:30:28FromDiscord<bluewhale_unkown_x> sent a code paste, see https://play.nim-lang.org/#pasty=wjwCaYwm
02:20:53*ftajhii joined #nim
02:22:47FromDiscord<liam029526> sent a long message, see https://pasty.ee/UzvCilAf
03:06:09*redj quit (Ping timeout: 252 seconds)
03:19:39*redj joined #nim
03:28:50FromDiscord<Elegantbeef> `lent openArray` makes little sense
07:01:44*tiorock joined #nim
07:01:44*tiorock quit (Changing host)
07:01:44*tiorock joined #nim
07:01:44*rockcavera is now known as Guest2291
07:01:44*Guest2291 quit (Killed (iridium.libera.chat (Nickname regained by services)))
07:01:45*tiorock is now known as rockcavera
07:09:26FromDiscord<enthus1ast.> Lately I see more pkgs with no nimble file (last one was treeform silky) . What do you all use now?
07:09:45FromDiscord<enthus1ast.> (edit) "Lately I see more pkgs with no nimble file (last one was treeform silky) . What do you all use now? ... " added "(For package management)"
07:11:03FromDiscord<enthus1ast.> Or @treeform would you add a nimble file? I would love to try it 😉
07:14:40FromDiscord<enthus1ast.> I have the feeling I should re install all nim related stuff, I still carry around pkg1 stuff from several years and nimble seems to be confused a little
08:36:19FromDiscord<lainlaylie> afaic a nim library without a nimble-conpatible nimble file is not a nim package and i will not be using it
13:59:11FromDiscord<treeform> In reply to @enthus1ast. "Lately I see more": Silky will have a nimble file. It’s just it’s not ready. I would have kept it private but I needed to share it with n people.
15:06:14FromDiscord<ieltan> The package management story of nim is starting to concern me with how many alternative are popping out theses days. I though Atlas was going to be it?
15:06:24FromDiscord<ieltan> (edit) "though" => "thought"
15:06:37FromDiscord<ieltan> And that some of the things Atlas was good at would be ported to Nimble
15:08:32FromDiscord<mjsdev> @ieltan I've gone ahead and started mine 😛
15:08:56FromDiscord<mjsdev> And @lainlaylie is gonna hate it given I couldn't care less about the nimble file... or package names
15:09:20FromDiscord<ieltan> We really need a cargo for Nim
15:09:59FromDiscord<ieltan> And I think atlas is the one thing closer to this
15:11:00FromDiscord<ieltan> And yeah unless it's for learning I don't think people using Nim will use a format that isn't nimble
15:11:54FromDiscord<ieltan> It's the one thing that is pretty good imo there's no reason to get rid of it
15:12:09FromDiscord<mjsdev> sent a code paste, see https://play.nim-lang.org/#pasty=rovmplgr
15:12:46FromDiscord<mjsdev> And the only thing names do is determine what it gets called in vendor
15:13:33FromDiscord<ieltan> I've never seen the `gh` uri before
15:13:44FromDiscord<mjsdev> it's shorthand for github
15:14:09FromDiscord<ieltan> It's not the actual link to the repository though... 😥
15:14:32FromDiscord<mjsdev> It can be?
15:14:42FromDiscord<mjsdev> I mean, make the link whatever you like
15:14:48FromDiscord<mjsdev> don't even include nim-lang repo
15:14:56FromDiscord<mjsdev> it's up to you
15:14:57FromDiscord<mjsdev> lol
15:15:36FromDiscord<ieltan> In reply to @mjsdev "The one I'm working": The overridable `source` property sounds good if you're planning on forking the entire nimble repository (nobody does that though afaik)
15:15:43FromDiscord<ieltan> What is meta?
15:16:06FromDiscord<mjsdev> Just a placeholder for now
15:16:20FromDiscord<mjsdev> You can add private repos
15:16:28FromDiscord<mjsdev> or a repo where you just overload a few packages
15:16:54FromDiscord<mjsdev> Like the example shows my packages in the packages section, but I'd probably create a mininim repo
15:17:33FromDiscord<mjsdev> sent a code paste, see https://play.nim-lang.org/#pasty=CpBQihCF
15:18:07FromDiscord<ieltan> What if I have multiple sources and packages of the same name in one of them, how does it handle that?
15:18:16FromDiscord<mjsdev> in order
15:18:20FromDiscord<ieltan> Like you know when you fork nimble
15:18:23FromDiscord<mjsdev> later ones replace older ones
15:18:33FromDiscord<ieltan> But how does the code know what which to reference
15:18:39FromDiscord<ieltan> (edit) "what" => ""
15:19:05FromDiscord<mjsdev> There's only ever one package name to repo
15:20:28FromDiscord<mjsdev> sent a code paste, see https://play.nim-lang.org/#pasty=emkzOJCP
15:20:29FromDiscord<ieltan> Why not use ssh for pulling from private repos instead so it's less confusing
15:20:46FromDiscord<mjsdev> ssh URLs are fine
15:20:59FromDiscord<mjsdev> As long as the URL works for git
15:21:03FromDiscord<mjsdev> doesn't matter what the URL is
15:22:00FromDiscord<mjsdev> If you really need to overload all your sources, you can just specify the URL you actually want in packages
16:01:04FromDiscord<tauruuuuuus> Obligatory xkcd for this n package managers situation lol↵https://xkcd.com/927/
16:01:51FromDiscord<tauruuuuuus> Btw I've been trying atlas and liking it a lot, really similar in ethos to go mod which I dig, what's the issue with that?
16:02:22FromDiscord<mjsdev> In reply to @tauruuuuuus "Btw I've been trying": Try moving your repository.
16:03:09FromDiscord<tauruuuuuus> Wdym
16:06:04FromDiscord<mjsdev> I mean there are all kind of problems that can be introduced when you do pretty straighforward things, like change a repository URL
16:24:03FromDiscord<nasuray> In reply to @ieltan "The package management story": Software has bugs but folks prefer to write their own solutions than work with legacy code, but nimble and atlas are both being actively developed and improved, the situation won't be magically resolved without concerted effort by the community to contribute (in the form of issues and PRs)
16:24:31FromDiscord<mjsdev> In reply to @nasuray "Software has bugs but": What if we believe the fundamental design of both is broken?
16:25:35FromDiscord<mjsdev> Should I open an issue like I did on xmlparser so it can be closed because there was some legacy decision to treat some entities different from others?
16:26:40FromDiscord<ieltan> Idk what's wrong about atlas
16:26:57FromDiscord<ieltan> It has some features that would be great in theory but lacks a lot of polish
16:28:16FromDiscord<ieltan> In reply to @nasuray "Software has bugs but": Well I agree with you I think we should focus on' what we have and improve it
16:28:24FromDiscord<mjsdev> atlas is definitely miles above nimble -- but this weird distinction between treating official packages different than non official is strange.
16:28:53FromDiscord<mjsdev> Whether or not the problems I'm seeing with it can be worked around, I don't know for sure, but my guess is no the way it downloads .nimble files
16:30:23FromDiscord<ieltan> In reply to @mjsdev "atlas is definitely miles": But you can literally just use the nimble format, you don't have to push it to nim-lang/packages
16:30:36FromDiscord<ieltan> There is nothing wrong fundamentally speaking with nimble as a format
16:31:06FromDiscord<mjsdev> The problem is the name <=> url mapping and/or any older mixed cases
16:31:23FromDiscord<mjsdev> the nimble format implicitly means your package is named whatever the .nimble file is named
16:32:17FromDiscord<mjsdev> In my particular case, I moved the repository at some point... through some crazy downloading of a bunch of ancient .nimble files, it picked that up somewhere, and said there was a conflicting URL for <name> and I had to add pkgOverrides
16:34:00FromDiscord<mjsdev> in my particular case, I was actually straight onto URLs at that point, but doesn't matter, cause it's still using a nimble file, so when it resolves a URL, it's still loading up all those nimble files with that name.
16:34:24FromDiscord<ieltan> Hmm yeah I can see why it can be annoying now
16:35:06FromDiscord<mjsdev> Also.... still respecting versions in nimble files is crazy
16:35:16FromDiscord<mjsdev> I realize it's a "fallback" of some sorts (or supposed to be)
16:35:39FromDiscord<mjsdev> but the only thing worse than packages having names that are attached in history is packages having versions that are attached in history
16:36:51FromDiscord<mjsdev> VCS should be the sole source of truth, if I force push over a tag, I should get that version on update.