proto_lambda

6 ms·

121.
by proto_lambda 4y ago
Some examples of commit messages it generates would be useful, especially compared to good commit messages like the ones usually found in the Linux kernel.
122.
by proto_lambda 4y ago
(2020): https://www.csiro.au/en/News/News-releases/2020/Australian-t...
123.
by proto_lambda 4y ago
> Because usize has a platform-dependent size and generally the logic of the program should be platform-agnostic. Fair point, but it really only matters if the overflow is handled gracefully. If it's handled as an unrecoverable erro
124.
by proto_lambda 4y ago
Some of these comparisons are a little lackluster - sure, the issues may be relatively easy to reproduce if you translate the C code 1:1 to (unsafe) Rust, but you wouldn't even have such code in the first place if you wrote idiomatic R
125.
by proto_lambda 4y ago
> long range EV That's called a train.
126.
by proto_lambda 4y ago
In headlinese, your sentence would be short for "Person holds excessively strict ideas about English grammar and English posts". Not a great example to make your point.
127.
by proto_lambda 4y ago
I have a feeling to author doesn't know what "parsing" means.
128.
by proto_lambda 4y ago
I don't think this project specifically is the work of Espressif, but rather a community effort. Not sure about the other things you mentioned.
129.
by proto_lambda 4y ago
Interesting that all its Haikus are 5-7-6, even if it can correctly tell you that it's supposed to be 5-7-5.
130.
by proto_lambda 4y ago
You must've misunderstood, your statement looks like both x and y are `int *`, but in fact only x is an `int *`, while y is an `int`.
131.
by proto_lambda 4y ago
Lying requires intent. This was a mistake, something that humans are well-known for making, and if the compiler is designed to assume otherwise, it borders on useless in the real world.
132.
by proto_lambda 4y ago
It's just an artifact of decompilation. It's the same operation in machine code (checking the MSB), there's no way to tell which one was used in the original source code.
133.
by proto_lambda 4y ago
The problem here is that the thing that "can't happen" isn't actually something that can't happen, it's something that isn't allowed to happen according to a many-hundred-page document that approximate
134.
by proto_lambda 4y ago
It's not a bug. This is perfectly acceptable behaviour according to the language standard. If anything, it's a standard bug.
135.
by proto_lambda 4y ago
Incorrect. Library features like the fallible allocation API are available to all editions, for better or worse - it also means you can't make breaking changes to the standard library ever, not even with a new edition. New language fea
136.
by proto_lambda 4y ago
> You can obviously only call common methods That sounds like trait objects/dynamic dispatch/`dyn`, which comes with runtime costs. > or have to pattern match later and have a way to tell them apart. That "way to tell t
137.
by proto_lambda 4y ago
How would that work in a memory safe language? Rust does have (named) untagged unions already (using the `union` keyword), but they are unsafe to use because there is no way to know statically which of the possible variants a given value co
138.
by proto_lambda 4y ago
`NonNull` is actually a wrapper around the pointer type, with the added invariant that the pointer cannot be null. The compiler is made aware of this, which allows `Option<NonNull<T>>` to be just a plain pointer, where the `None
139.
by proto_lambda 4y ago
It's definitely not a data structure that makes the borrow checker happy. Luckily it's also not a data structure that's required or desirable in 99% of cases, but the standard library still offers an implementation for those
140.
Generic associated types to be stable in Rust 1.65(blog.rust-lang.org)
39 points by proto_lambda 4y ago|0 comments
141.
by proto_lambda 4y ago
> I feel like the author must know this The author does know this, it's a reference to a couple paragraphs above: > [...] and the HTTP protocol version, which is a fixed string which is always set to HTTP/1.1 and nothing els
142.
by proto_lambda 4y ago
cargo is not a binary distribution.
143.
Compiler optimizations are hard because they forget(faultlore.com)
44 points by proto_lambda 4y ago|4 comments
144.
by proto_lambda 4y ago
> - Don't forget to send reminder messages to everyone who RSVP'd leading up to your event. I like sending my reminder messages 1 week prior, 4 days before, and then on the morning of. I'd perceive that as too many. Leave
145.
by proto_lambda 4y ago
You need to communicate clearly that you are doing these things as a learning exercise, not just because they're a requirement for something bigger that you're actually trying to do. People try to be helpful by saving you unnece
146.
by proto_lambda 4y ago
Neonazis are not a protected class (or equivalent in your jurisdiction).
147.
by proto_lambda 4y ago
The hosting provider is free to decide who they want to host and who they don't want to host. If they're fine with being known for knowingly hosting the scum of the earth, more power to them; but they are also absolutely allowed t
148.
by proto_lambda 4y ago
HN title mangling strikes again. "NaN Boxing", which is very likely what the OP submitted it as, would've been obvious.
149.
by proto_lambda 4y ago
> - Raw-pointer equivalent to lifetime parameters (`GenericStruct<*>`, converts `&'a T` into `*const T` and `&'a mut T` into `*mut T`) How would that work? References and pointers are fundamentally different types
150.
by proto_lambda 4y ago
No idea, but from context, maybe they meant https://en.wikipedia.org/wiki/Multiple_Dwelling_Unit ? Really weird phrasing either way.

More ›