540 Followers
121 Following
2.2K Posts
the one who is workingjubilee @ the birdsite

@penguin42 @gregkh Rust's type system persists into `unsafe` blocks, including e.g. lifetime checks. The remove function itself depends on two lifetime-bound entities and relies on the fact that the references are real to prove certain operations are correct to perform.

The problem is the safety requirement for this function is "leaky", because it includes a requirement about *other* lists. This safety requirement was one chosen by the kernel programmers, though, not Rust.

strange .so files lying in /lib folders is no basis for a system of plugins
@MarcoIeni @jyn @flaki yeah this seems like an unfortunate but necessary case of "when in beancounter hell, shuffle the beans", and I am very glad you are done shuffling beans! The benefit remains real to someone even if it is motivated by someone somewhere being absurd.
@david_chisnall Rust's `str` can contain '\0' in the middle, as the 0 byte is a valid UTF-8 value. You're not even wrong.
@enigmatico @bagder @ar we're a tool-using species. if you don't like that we use tools, then put down the tool you used to send these messages.
@timorl @tjhexf all hail "work to rule"

Signal provides:

- Excellent protection against third party interception of communications (wiretapping).

- Limited protection against compromised (hacked) or lost devices

- No protection against certain common usage mistakes (accidentally including a reporter in your large group war planning chat).

Being a Linux power user is a terminal condition.
Are you a...?
Dom
7%
Sub
21.7%
Switch
22.9%
Switch 2
48.3%
Poll ended at .