In reply to @irenes:matrix.org
against my better judgement I reiterate that the overwork situation is the result of the communication debacle and that waiting for overwork to be resolved before thinking about communication is a death spiral

In reply to @kfears:matrix.org
I appreciate the very deep thought that goes into infra choices, tooling, integration work, releng, and more; but it feels like those things burn out people really hard and can be offloaded to other people more

What is the difference between realPath(path) and canonPath(path, true)?

/**
 * Canonicalise a path by removing all `.` or `..` components and
 * double or trailing slashes.  Optionally resolves all symlink
 * components such that each component of the resulting path is *not*
 * a symbolic link.
 */
Path canonPath(PathView path, bool resolveSymlinks = false);

/**
 * Resolves a file path to a fully absolute path with no symbolic links.
 *
 * @param path The path to resolve. If it is relative, it will be resolved relative
 * to the process's current directory.
 *
 * @note This is not a pure function; it performs this resolution by querying
 * the filesystem.
 *
 * @note @ref path sadly must be (a reference to) an owned string, as std::string_view
 * are not valid C strings...
 *
 * @return The fully resolved path.
 */
Path realPath(Path const & path);

In reply to @piegames:flausch.social
Horrors and I are already working quite a bit on the evaluator, but rewriting the GC is still open :)

In reply to @piegames:flausch.social
jade_: I've heard you want to cut a release Very Soon, what's your opinion on including vs not including https://gerrit.lix.systems/c/lix/+/2190 in the release? It's a mildly breaking change, do we want to get it out early to gather feedback or do we want to have it on main for a while in the hope that the beta testers will catch any issues until the next release?

In reply to @piegames:flausch.social
In terms of intro-level tasks, one other thing which can be done which is not cursed C++ for once is to look at the functional2 test runner. Probably the solution is to write our own test runner (Python or not) or to find another one which doesn't scare itself when run with more than 1 thread …

In reply to @raitobezarius:matrix.org
I agree and I do not see any good solutions until the overwork situation decreases and we can dilute enough responsibilities (release engineering, etc.) so that we stop putting prolific project members into risky situations for themselves

i happen to be in seattle at the moment and i might do some irl work with wiggles on trying to get releng into a better state.

my view of my role is to try to shepherd acceptable code in as much as possible and try to reduce dependencies on myself and core. one related thing is that we have, for basically accidental reasons, not simply given away commit access to more competent qualified people, which is 100% a governance problem of not being quorate enough due to inactivity but also that i think we just need to simply be giving it away harder with less specific requirements. there is still also the open question of what the difference should be between core and commit access (since core is already too many people to be easily quorate and obviously needs governance reform, but this takes such immense energy that i dont know if people have it)