estebank

7 ms·

61.
by estebank 5mo ago
Rust macros are Token Trees and provide namespace hygiene, so not quite "text in, text out".
62.
by estebank 5mo ago
That kind of code doesn't have to hurt performance, as long as monomorphization, inlining or JITting are available to the toolchain. If every single method access is a virtual-table call, then yes, there's an "unnecessary
63.
by estebank 5mo ago
VB had case insensitive name resolution.
64.
by estebank 5mo ago
VisualBasic did that. I think it is a mistake. But that doesn't mean that the compiler can't detect that and tell you how to fix it instead.
65.
by estebank 5mo ago
If you had a "canonical datastructure database", you could have very short annotations on every standard library for any language that indexes a function to their canonical name. After that you only need to update the database.
66.
by estebank 5mo ago
In the Rust toolchain we've done the same. It just so happens that rustdoc already has introduced annotations for "aliases" so that when someone searches for push and it doesn't exist, append would show up. Having those
67.
by estebank 5mo ago
Concepts support (like traits I'm Rust) is necessary for good diagnostics, but not sufficient . It gives you the architecture and metadata that you require to infer what the user wants, but a lot of additional analysis on the decisi
68.
by estebank 5mo ago
Even without having concepts, a cpp compiler could conceivably detect at definition time that the template is acting as a generics declaration only, and treat it specially as if it was a "late-bound concept". That would potentia
69.
by estebank 5mo ago
> LLMs are 100% better because they'll give me an answer without trying to sell me their thing or pump me with ads. Yet.
70.
by estebank 5mo ago
You can detect with high confidence that a player is aiming at something that shouldn't be visible to them. That goes for both aim bots and wall hacks. The longer they play and the more they do it, the higher the confidence. If you don
71.
by estebank 5mo ago
Steak doesn't look like a cow either.
72.
by estebank 5mo ago
There's no reason that kind of client behavior can't be detected server side.
73.
by estebank 5mo ago
Most of the time is spent figuring what the right thing to do is, not writing the implementation. Sometimes the process of writing the implementation surfaces new considerations about what the right thing is, but still, producing text to fe
74.
by estebank 5mo ago
> The UFO nut community is being weaponized for political leverage Always has been, at least since 1947.
75.
by estebank 5mo ago
Please don't, at least not mimicking the "edgy 13 year old thinks it comes across as cool" tone.
76.
by estebank 5mo ago
If the toolchain crashed while compiling, please file a ticket! That shouldn't happen ever and if it does it is indicative of a big problem that needs fixing.
77.
by estebank 5mo ago
Firefox explicitly opts out of stability guarantees by using nightly features on a stable compiler in an unsupported manner, not dissimilar to using an unstable GNU extension in C. But good example of the caveat that if you're not usin
78.
by estebank 5mo ago
I think the divide is apps vs libraries: a library that requires their dependants to set an environment variable opting out of stability guarantees is unlikely to gain adoption, but applications that do so are more common, like Firefox.
79.
by estebank 5mo ago
Under that rubric, no language is memory safe .
80.
by estebank 5mo ago
This attitude doesn't even work in carpentry, depending on the timeframe you look at, tools have changed over time. You can still use a hand saw, where a table saw would be just as suitable, or have a SawStop(tm) and reduce the likelih
81.
by estebank 5mo ago
Do you recall which libraries? Use of nightly fell of a cliff after 2018. Looking at the bottom of https://lib.rs/stats#rustc-usage , ~8% of all crates.io requests came from a nightly newer than that corresponding to 1.86. T
82.
by estebank 5mo ago
In many countries the state owned the phone company.
83.
by estebank 5mo ago
Code in all languages bitrots. Even if your dependencies are "done", the language is unchanging, the toolchain mature, a vendor can introduce a new platform and all of a sudden your code won't compile anymore, because IBM int
84.
by estebank 5mo ago
Even if a crate is yanked, if you have the version in a lock file it will still download and build. (This was done precisely after seeing the left-pad incident.)
85.
by estebank 5mo ago
Do you remember more specifics? I've seen four cases: - a project with no Cargo.lock, where there have been breaking changes in a dependency that wasn't specific enough in Cargo.toml; fixing this requires some finessing of depende
86.
by estebank 5mo ago
Can you point at any piece of code from 5 years ago that doesn't work today?
87.
by estebank 5mo ago
Your customers should be proper Spaniards and be watching the match, hence not noticing the downtime! /s
88.
by estebank 5mo ago
On the one hand, I would tend to agree that making things painful enough might force people to stop ignoring and improve things. On the other, after seeing waves hands at everything since 2016 makes me very skeptical of accelerationism: s
89.
by estebank 5mo ago
Delaying the run of clippy until CI would be annoying, because then you'd get a build failure for something that was preventable and could have been quickly addresses during development before pushing. Just feels like a pebble in your
90.
by estebank 5mo ago
>>> I don't care, I run Graphene, and my phone is definitely mine. I really don't see an implied "and you can too".

More ›