Jubilee

@rustbot label: +O-linux

I recommend that because fish sessions are persisted that we detect fish during setup and direct the user to simply run the command which sets PATH appropriately, possibly after writing...

That is a type error. Such a compiler error will always fail. Using or not using `-Dwarnings` should have no effect on it. In addition, I can pull and build...

I noted whether I could compile the crate at all, because when dependencies are compiled with Rust, they are compiled with `--cap-lints=allow`. Thus, as I understand it, denying warnings or...

Hello. I am not the author of this crate, nor a maintainer of it, and so I have standing neither to approve or deny this pull request. However, I was...

Hello. I am speaking as merely an individual and my remarks should not be considered an official stance from the Rust project or anything like that. However, it is my...

I will refer to these hypothetical targets `x86_64-unknown-linux-postgres` `aarch64-unknown-linux-postgres` This follows the established convention of using the last term in the target tuple to define the ABI and necessary runtime...

I am going to focus on trying to get the latest Postgres working and pretend that doesn't happen in ways that actually impact the extent of alloc/std we want to...

Since trying to stuff Rust fully "into" the Postgres server's allocation and error handling logic is the main goal for this, I spent a fair amount of time studying Postgres's...

We lose it twice, actually: Rust's libcore doesn't have `std::thread`, so `#![no_std]` means no threads. It might be possible to do something clever to recover this ability, but it's definitely...