proto_lambda

The whole point of commit hashes is that you can't do that, so no, being able to change history undetected would not be nice at all.

Thanks! That's way too well hidden.

Something like that could probably be built on top of the matrix protocol, I'm not aware of anything concrete though.

In principle I can agree that Rust (like so many things in tech) is a bit of a sausage fest, and that women can, in my experience, often be better leaders than men especially when it comes to emotional/communication matters like with this whole mess.

The wording "real woman" however immediately smells like an attempt to exclude trans women, of whom there are quite a few in the Rust community - even if that wasn't your intention at all, it might explain at least some of the downvotes though.

> has anyone tried blasting them with sound

That's likely why they're attacking boats in the first place.

Yes, I don't know of any TOTP authenticator that doesn't work fully locally (disregarding things like key backups).

All it requires is the initial setup key and a somewhat accurate (~30s) time source.

Give https://en.wikipedia.org/wiki/Time-based_one-time_password#A... a read, it's extremely simple.

> Just answer the fricking question or I'll replace you with a bot.

Please do, it'll save everyone a lot of time and headache, especially if this is representative of your usual mode of communication.

It's TOTP, a very simple and universal standard, you can use any application you want - many password managers support it as well.

That's also a highly effective mitigation against legitimate users, especially those already disadvantaged everywhere else by a lack of disposable income.

Because that's not a type in Rust. I don't understand where you're going with this.

What is machine-specific about i32? It's a signed 32-bit integer, regardless of the machine you're on.

It can capture things, OP's example does not capture anything.

> That would not compile

It does compile.

> because `x` does not have the type `fn (i32, i32) -> i32` (that's reserved for "normal" functions).

Closures can cast to function pointers just fine as long as they don't capture anything.

It is commonly used as a short form of vorophilia, i.e. sexual pleasure from (the idea of) being eaten/eating somebody, usually only in a fantasy rather than realistic context from what I gather.

I'd be surprised if there was anywhere in the UK where modern low-temperature heat pumps regularly don't work.

I think you're off by a couple orders of magnitude there. 25e3 errors/(1e9 h * 1e6 b) = 25e-12 errors/hour/bit, ~~or 4 errors/hour/terabyte.~~

Edit: nope, I got that last step wrong, it's actually 200 errors/hour/terabyte, or 1 error/gigabyte/5 hours, pretty close to what you said.

Three weeks aren't a gap, that's just a little time to relax between jobs.

That's not even remotely similar.

The author really doesn't have to convince anyone, "please don't do $X" is more than enough to state their wish for you not to do $X.

That's exactly what OP's footnotes say, yes.

> FPGA doesn't have the instruction pipeline as the command is encoded in the gates themselves. It means that on runtime the FPGA is not turing complete[0] as opposed to the CPU[1].

That obviously depends entirely on the circuit, many sufficiently advanced circuits probably end up being accidentally turing complete.

> I miss how in Ada you can define which values an int can have. Can you do that in Rust?

yes, kind of: https://crates.io/crates/deranged

It'll take another while until const generics on stable are advanced enough to make this properly usable, such that e.g. `RangedU32<3, 10> + RangedU32<5, 6> = RangedU32<8, 16>`.

> I had an eco friendly washing machine

I'm surprised the plates survived at all, I guess you didn't use the spin cycle?

Kidding aside, dishwashers, even new ones, should be perfectly capable of cleaning your dishes in a single cycle unless they've been left to dry out for days, are stacked improperly, or the detergent isn't dosed correctly. It's always worth consulting the manual for tips as well.

Who are you arguing against? You are just repeating the comment you replied to.

So it's an art installation reminiscent of a sundial, not an actual sundial.

The C equivalent would be a bunch of `in_addr`/`sockaddr_in`/`sockaddr` handling where you can do something wrong at basically every step of the way. You can't mess up the types in Rust, there's only one way they fit together.

Of course if you just want to convert a string to a SocketAddr (returning an error at runtime if it's invalid), you just do `let addr = "127.0.0.1:8080".parse();`.

> a Rust program which relies on this for a constant

https://godbolt.org/z/ceY3q3eW4

Bad example because that's a library feature and doesn't involve explicit compiler support - in general you're right though, backwards-compatible compiler features (say, GATs) are added regularly and are available for all editions, not just the newest one.

"abled" is the term your looking for, yes.