!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

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

Load older messages

SenderMessageTime
17 May 2024
@julia:the-apothecary.clubjuliai'm a bit lost; as in, isn't that affecting the build of the lix derivation?02:38:58
@jade_:matrix.orgjade_yes02:39:05
@julia:the-apothecary.clubjuliaoh wait yep02:39:08
@jade_:matrix.orgjade_which has the tests run in it02:39:08
@julia:the-apothecary.clubjuliatests run in the derivation02:39:11
@jade_:matrix.orgjade_and the tests can't access localhost -> explode02:39:15
@jade_:matrix.orgjade_yeah02:39:16
@julia:the-apothecary.clubjuliawelp, pushed, time to wait for the builder to run (and probably fail on remote builders shenanigans)02:42:08
@jade_:matrix.orgjade_if you need a darwin computer, we can get you access to the darwin-build-box02:43:37
@jade_:matrix.orgjade_https://nix-community.org/community-builder/ i can get you access to this02:43:59
@julia:the-apothecary.clubjuliaif I keep doing things can probably consider it :)02:44:49
@jade_:matrix.orgjade_image.png
Download image.png		02:55:58
@jade_:matrix.orgjade_alriiiighty we have horrible forgejo code02:56:03
@qyriad:katesiria.orgQyriad Fuck yeah 02:59:56
@jade_:matrix.orgjade_we have shipped the bad forgejo code03:05:51
@lunaphied:lunaphied.meLunaphiedHell yeau03:06:02
@lunaphied:lunaphied.meLunaphied* Hell yeah03:06:08
@jade_:matrix.orgjade_https://gist.github.com/lf-/f2e31a329c3c48f09198c865e21618e603:08:46
@jade_:matrix.orgjade_for those who want to see the patches03:08:51
@julia:the-apothecary.clubjuliaoh yeah a bunch of the imported isses link to NixOS/nix#4324 etc but they're treated as repos that exist on forgejo and not on github which makes clicking them annoying03:30:23
@jade_:matrix.orgjade_sigh yes04:10:06
@jade_:matrix.orgjade_can't do much about that04:10:10
@jade_:matrix.orgjade_you should plausibly have access to just edit those issues to fix the links tho?04:10:32
@julia:the-apothecary.clubjuliaoh I seem to don't I04:58:41
@julia:the-apothecary.clubjulia
In reply to @jade_:matrix.org
can't do much about that
nginx redirect 😂 		04:59:04
@julia:the-apothecary.clubjulia
In reply to @jade_:matrix.org
can't do much about that
* nginx redirect 😛 		05:15:32
@ifreilicht:matrix.orgiFreilicht joined the room.08:01:16
@grimmauld:grimmauld.deGrimmauld (moving to @grimmauld:grapevine.grimmauld.de)I'm still waiting for the forgejo federation stuff to be useable08:15:04
@414owen:matrix.orgOwen Shepherd joined the room.20:22:16
@414owen:matrix.orgOwen Shepherd

👋 Hello,
Nice to meet you all!
I'm Owen, I write compilers and things, with a focus on compile-time performance.
Let me preface this by saying I know there's a feature freeze, and I'm happy if what I'm working on remains a personal project until that changes :)
Aaaanyway, I'm working on adding bytecode-interpreter to nix/lix (whichever project(s) want to upstream it).
The plan for MVP, is leave everything as-is upto lixexpr, and add a writeBytecode function to Expr.
This will write out bytecode as C-abi POD, and then... well there will be a bytecode interpreter :)
I'm gonna write that in C, probably, but because it's C POD, there's nothing stopping the interpreter being in rust, or any other language...
Bytecode mode will enabled by some kind of command-line flag, or maybe a config value in nix.conf.
This might end up being slower than the current tree-walk evaluator, in which case... experiment complete.

Anything else I should keep in mind, assuming I want to maximise my changes of upstreaming this?
Any thoughts in general?

20:46:50

Show newer messages

Back to Room ListRoom Version: 10