 | Lix Development | 424 Members |
| (Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel. | 141 Servers |
| Lix Development | 424 Members |
| (Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel. | 141 Servers |
| Sender | Message | Time |
|---|---|---|
| 17 Mar 2026 | ||
 zoë (she/her) joined the room. | 00:10:50 | |
| zoë (she/her) | this is probably very dumb but: I'm trying to follow "Getting Started with Gerrit", and since it specifically points out "Now you can just git commit your change. No need to create a separate branch", i committed on main directly, but then the no-commit-on-branch commit hook failed because i tried to commit to main, so... am i missing something? | 03:11:46 |
 Lisanna | It's still probably a good idea to separate your changes into their own branches, otherwise you'll have to rebase just to edit changes that happened before you make another, unrelated change | 03:16:34 |
| zoë (she/her) | right, that makes sense, i was just a little confused at the docs ^^; | 03:17:23 |
| zoë (she/her) | aaaand first CL submitted :D ...it's an 8-bytes diff x) | 03:24:38 |
| Lisanna | * | 03:58:07 |
 piegames | In reply to @blokyk:matrix.orgI think that sentence was about remote branches, but you're right it's confusing | 09:14:57 |
| 18 Mar 2026 | ||
| zoë (she/her) | hi, i recently got a review on one of my CLs (by eldritch horrors / pennae but they're not in this room ;-;), about using std::next to traverse a nix::Generator<T>, but i'm not very good with c++ so i'm not sure how to do that, since it seems that nix::Generator<T>.next returns a custom iterator implementation that differs from c++'s | 12:20:03 |
| zoë (she/her) | * hi, i recently got a review on one of my CLs (by eldritch horrors / pennae but they're not in this room ;-;), about using std::next to traverse a nix::Generator<T>, but i'm not very good with c++ so i'm not sure how to do that, since it seems that nix::Generator<T>.next returns a custom iterator implementation that differs from c++'s(specifically, writing either std::next(gen.next()) or std::next(gen) gets me Candidate template ignored: substitution failure [with _InputIterator = iterator]: argument may not have 'void' type) | 12:21:50 |
| zoë (she/her) | * c++ noob time: hi, i recently got a review on one of my CLs (by eldritch horrors / pennae but they're not in this room ;-;), about using std::next to traverse a nix::Generator<T>, but i'm not very good with c++ so i'm not sure how to do that, since it seems that nix::Generator<T>.next returns a custom iterator implementation that differs from c++'s(specifically, writing either std::next(gen.next()) or std::next(gen) gets me Candidate template ignored: substitution failure [with _InputIterator = iterator]: argument may not have 'void' type) | 12:27:21 |
 Qyriad | That comment is non-blocking (it's marked as "Resolved"), so it's not a huge issue if you can't figure that out | 12:27:19 |
| Qyriad | But the comment does also specify that it would have to be something like std::next(traces.begin(), requestTraceIdx) | 12:28:03 |
| zoë (she/her) | yeah i saw but i figured i'd like to do it anyways, since that loop is quite weird to me | 12:28:10 |
| zoë (she/her) | yeah yeah i also tried that (the second arg is optional and defaults to 1), i simplified it for the comment but i'll edit it | 12:28:55 |
| zoë (she/her) | * c++ noob time: hi, i recently got a review on one of my CLs (by eldritch horrors / pennae but they're not in this room ;-;), about using std::next to traverse a nix::Generator<T>, but i'm not very good with c++ so i'm not sure how to do that, since it seems that nix::Generator<T>.next returns a custom iterator implementation that differs from c++'s(specifically, writing either std::next(gen.next(), idx) or std::next(gen, idx) gets me Candidate template ignored: substitution failure [with _InputIterator = iterator]: argument may not have 'void' type) | 12:29:05 |
 raitobezarius | FYI, it's easier to reach out for development discussions over zulip.lix.systems ; if you plan to contribute more actively, I recommend joining it :) | 13:09:34 |
| zoë (she/her) | i've already made an account for it (because for some reason i couldn't join the matrix spaces before), but i'm not too good in more formal environments (at least to me zulip feels more formal) ;-; and i think the amount of things i can contribute given my skillset is not gonna be very high, especially given the time constraints i'll be in soon enough x) | 13:11:46 |
| zoë (she/her) | anyway, i hesitated doing that this time, but i'll do it next time then :) | 13:12:16 |
| zoë (she/her) | * anyway, i hesitated doing that this time, but i'll do it next time then, thanks for the clarification :) | 13:12:22 |
| raitobezarius | i'd say zulip is meant to make conversations more structured to help us to help you or help yourselves follow what you care about on a development level | 13:15:46 |
| raitobezarius | (sure, it's less tolerant of offtopics tangents but that's a feature :P) | 13:16:01 |
| raitobezarius | but no problem, this was just an invitation | 13:17:07 |
| zoë (she/her) | i saw on the wiki you were talking about maybe retiring the matrix anyway given the infrastructure problems with it (though i'd be sad to see it go given my reasons above), so i guess i might have to get used to zulip at some point :p | 13:17:40 |
| piegames | As per the recent meeting on this, Matrix will stay with a slightly reduced channel list | 13:39:22 |
| 16 May 2024 | ||
 zrsk joined the room. | 13:54:49 | |
 samrose | In reply to @lunaphied:lunaphied.meThe other thing that I could do if it helps is test things and try to find bugs. I did do some C++ work in the past, but may lack the time to do it justice here at least for about 30 days or so | 15:55:29 |
| Qyriad | we are not in any rush 🙂 | 17:20:53 |
| samrose | Would it help to also test out the existing Lix code and try to find issues/bugs etc? | 17:23:21 |
| Qyriad | absolutely | 17:23:41 |
| samrose |
| 17:23:48 |