estebank

56 ms·

751.
by estebank 3y ago
Whenever you see weasel words like that, it means the compiler knows that the issue you encountered could be what it is saying but the necessary metadata to figure out for sure is inaccessible to it. It's the problem with classical s
752.
by estebank 3y ago
That is a different problem than the one I thought you were seeing. We do spend a lot of time trying to silence errors that are irrelevant. We also get a lot of complaints when fixing a single error produces a wave of new errors that were h
753.
by estebank 3y ago
It could also be stated as "1/5 of crates interface with the OS, FFI, or hardware or use pointers for fancy data-structures".
754.
by estebank 3y ago
Note that a crate having any unsafe and having unsafe all over the place are two different things.
755.
by estebank 3y ago
Instead of looking at the crates themselves, you might want to check your (or others') Rust application with https://github.com/rust-secure-code/cargo-geiger to get a sense of effective prevalence. I also dispute
756.
by estebank 3y ago
If you want to check your dependency tree for the number of maintainers you're dealing with instead of the number of dependencies, this can be done with cargo tree + checking the Cargo.toml/crates.io ownership info for each of the
757.
by estebank 3y ago
80% of crates have no unsafe code in them.
758.
by estebank 3y ago
I believe this is in our radar and waiting on the new trait solver, but just in case if you have a repro I would appreciate a ticket to improve the diagnostic.
759.
by estebank 3y ago
I would encourage you to file tickets whenever you encounter deficiencies in the tooling, including bad diagnostics. We take them seriously. As for whether our efforts are accomplishing anything, trying out older releases can be eye opening
760.
by estebank 3y ago
That doesn't really work. All unsafe lets you do is dereference pointers or call unsafe functions. That's not gonna speed your development up during prototyping. You can instead wrap everything in Arc<Mutex<T>> and .cl
761.
by estebank 3y ago
As one of the main people working on Rust compiler diagnostics, I find this comparison beyond distasteful. The tooling is not capricious in its restrictions and we go out of our way to make it communicate to people with as much empathy and
762.
by estebank 3y ago
This is a good call-out, the issue around vendoring, but it seemed to me that the complaint was about using BoringSSL at all. It is a very valid complaint if dependencies are vendoring their dependencies, side-stepping your system. On Rust-
763.
by estebank 3y ago
It doesn't help with the failure mode of dependencies disappearing, which forces people that care about it to vendor, which in turn brings its own set of issues.
764.
by estebank 3y ago
The critique was that it relies on C code for cryptography at all, no further investigation on whether the usage of those APIs is limited to providing safe abstractions. That's what I take issue with.
765.
by estebank 3y ago
> Swift was sold to me as a safe language. But I think it would be more accurate to describe it as a thin veneer of safety over a deep pit of peril. The linux version of swift replicates a large number of native mac frameworks using what
766.
by estebank 3y ago
Paving over every square inch of the country is the opposite of a solution. The more we entrench ourselves everywhere, the more we are affected by natural phenomena like forest fires and flash floods. And that is without even considering th
767.
by estebank 3y ago
It's mnemonic! [S]top and [Q]ontinue :o)
768.
by estebank 3y ago
Appreciate the vote of confidence, but I fear the default output isn't great for this usecase. In that example, you're cutting out the main message, file position and any message that comes after. It is also a single span in the m
769.
by estebank 3y ago
With --error-format=json you can get both the underlying encoded tree as well as the cli output within a field. The later is useful for tools that don't want to do anything special beyond presenting the output inline. All the pieces ar
770.
by estebank 3y ago
For a while now I've been meaning to do something about this. Users of TTS interfaces and braille displays can currently rely on whatever LSP compatible IDE they might use, but I would like to provide cli output that is suitable for th
771.
by estebank 3y ago
> But integer arithmetic is safe in terms of Rust. To expand on this: integer overflow is not UB, it is unspecified. It can result in clamping, wrapping or a panic, depending on configuration at compile time. > In release mode, it use
772.
by estebank 3y ago
That could indeed be done (and I want to make that happen at some point), but you must be aware that this is an optimization, and as such trivial unrelated code changes can make the compile times balloon because all of a sudden you added a
773.
by estebank 3y ago
They spiced it up, now there's a Stephan and an Esteban in the mix.
774.
by estebank 3y ago
> For example, the error messages in Elm are just insanely better than in any other language I know. Like, it's not even in the same ballpark. Why doesn't every language have this? It's a combination of economics (who pays
775.
by estebank 3y ago
> Updating compiler version (minor update) broke existing code Could you elaborate on that? That's not something that's supposed to happen and if it has, I would like to make sure we register it in our issue tracker.
776.
by estebank 3y ago
American school shootings are news across the world. Why doesn that copy cat effect affect other countries?
777.
by estebank 3y ago
American school shootings are news across the world. Why doesn that copy cat effect affect other countries?
778.
by estebank 3y ago
You're wrong. https://www.chem.purdue.edu/chemsafety/Training/PPETrain/dbl...
779.
by estebank 3y ago
The thing that I don't get is that when I was growing up on Argentina, I never saw anything like that. We heard about the shootings and bomb threats in the US, but once a teacher got stabbed in an Argentinean school and was national ne
780.
by estebank 3y ago
I make it a point to seek out negative opinions of the projects I work on, because a lot of the time there's at least a kernel of a bug report behind every complaint. > BULLSHIT!!! > Have you tried listening to yourself? But thi

More ›