!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

435 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.145 Servers

Load older messages


SenderMessageTime
17 May 2024
@414owen:matrix.orgOwen ShepherdDo you know if @pennae has any code or plan I can look at, to see what the direction is?21:19:21
@jade_:matrix.orgjade_it's not feasible to do that until we fix the io model (wip), which is blocking the parser rewrite (done but needs them to backport), which is blocking fixing more of the evaluator21:25:04
@raitobezarius:matrix.orgraitobezarius (DECT: 7248)
In reply to @414owen:matrix.org
Yes, I've had a look already. I was looking to improve a nix implementation I can actually use now, which has an ecosystem, rather than hack on tvix, which (I assume) isn't going to be usable for a while.
Well, making Tvix usable now is potentially in the same range of efforts than carving a bytecode interpreter in CppNix right now.
21:34:15
@jade_:matrix.orgjade_i would also say that it is probably a more worthwhile use of time, because i think it is highly unlikely we would accept this approach21:46:15
@lunaphied:lunaphied.meLunaphied changed their display name from Lunaphied to lunaphied.21:47:32
@414owen:matrix.orgOwen ShepherdSure, what would you change about the approach? I was looking for that kind of feedback.21:51:17
@Ericson2314:matrix.orgJohn Ericson
In reply to @jade_:matrix.org
it's not feasible to do that until we fix the io model (wip), which is blocking the parser rewrite (done but needs them to backport), which is blocking fixing more of the evaluator
oh it is neat to see the dependency graph
21:52:07
@Ericson2314:matrix.orgJohn Ericson I wanna rename *::Recursive in Nix to *::NixArchive 21:53:22
@Ericson2314:matrix.orgJohn Ericsonbecause recursive is a terrible name21:53:29
@Ericson2314:matrix.orgJohn Ericsonand it would be cool if you all could do the same sed21:53:35
@Ericson2314:matrix.orgJohn Ericsonso it isn't a needless cherry-picking stumbling block21:53:45
@jade_:matrix.orgjade_
In reply to @Ericson2314:matrix.org
so it isn't a needless cherry-picking stumbling block
hahahahaha wanna fix our includes to use lib* across both projects,
22:00:32
@jade_:matrix.orgjade_i have a clang-tidy pass for it22:00:44
@Ericson2314:matrix.orgJohn Ericson lib*? 22:06:39
@Ericson2314:matrix.orgJohn Ericsonit would be neat if we supported the same C APIs22:07:02
@Ericson2314:matrix.orgJohn Ericsonbut that could be hard22:07:09
@puck:puck.moepuckwe're looking into it, but do have some strong opinions and aren't married to exact ABI compatibility at least22:11:20
@Ericson2314:matrix.orgJohn EricsonI heard concern about ours being too strict right now22:17:03
@Ericson2314:matrix.orgJohn Ericsonre langauge22:17:05
@Ericson2314:matrix.orgJohn Ericsonbut I think we had the same concern22:17:09
@Ericson2314:matrix.orgJohn Ericsonso that alone shouldn't be a deal-breaker22:17:16
18 May 2024
@jade_:matrix.orgjade_
In reply to @Ericson2314:matrix.org
lib*?
libexpr/*.hh, etc
01:52:34
@Ericson2314:matrix.orgJohn Ericson jade_: not libnixexpr? 02:00:04
@Ericson2314:matrix.orgJohn Ericson * jade_: not libnixexpr or liblixexpr? 02:00:09
@Ericson2314:matrix.orgJohn Ericsoninteresting02:00:11
@Ericson2314:matrix.orgJohn Ericsonor nix/expr/foo.hh?02:00:30
@Ericson2314:matrix.orgJohn Ericson * or nix/expr/foo.hh? 02:00:32
@Ericson2314:matrix.orgJohn Ericson (and likewise with lix) 02:00:48
@jade_:matrix.orgjade_well, externally it would be nix/libexpr/*.hh or so.02:02:28
@jade_:matrix.orgjade_ * well, externally it would be lix/libexpr/*.hh or so. 02:02:42

Show newer messages


Back to Room ListRoom Version: 10