epage

11 ms·

91.
by epage 2y ago
> I would have contributed patches to address these shortcomings if it were not for my third criticism, which addresses the elephant in the room: Jujutsu is a Google employee’s “20% project”, and thus all contributors are required to sig
92.
by epage 2y ago
‘jj split`isn't a workaround but their version of `git add -p`. The intent is to make the Index unspecial to make it easier to work with and not to get rid of it. If there are usability gaps between the jj's active commit and git&
93.
by epage 2y ago
Mixing editions in a file happens in Rust with the macro system. You write a macro to generate code in your edition and the generation happens in the callers crate, no matter what edition it is.
94.
by epage 2y ago
This term is coming up more frequently in the C++ community as they discuss Rust's safety features so to add more nuance to the discussion and focus on subsets of the problem to solve. Note that there are some more heated takes on wher
95.
by epage 2y ago
For Rust, yes, we do have that and that'd be great to generalize it. That was a C++ code base using custom lock types that I used a regex linter for. Glad to not be touching it anymore for many reasons.
96.
by epage 2y ago
Completely agree. I'm only calling it out because of the claim "perfectly conformant with the standard".
97.
by epage 2y ago
Looking over https://en.cppreference.com/w/cpp/compiler_support , it seems there is good conformance on C++11 and C++14 but there are gaps on C++17+ among gcc, msvc, and clang.
98.
by epage 2y ago
Thanks for the reply! There is a bit to dig in here. Mind reposting this on a discussion so i get notifications and it easier to find again in the future?
99.
by epage 2y ago
For a C++ programmer, the related "suprising" equivalent is to not name the variable. We had a regex linter in our code to ensure locks were named because of bugs from this.
100.
by epage 2y ago
I feel like the intent of this article is ambiguous. It reads like there is no interest for a descriptive standard and is arguing for one. However, it ends by calling out the standard work in a single sentence. I was expecting to have to ca
101.
by epage 2y ago
Except for the most trivial programs, clap should not make a factor of 10 difference, especially for incremental builds. For serde, I can see it if you use it a lot. There is an experiment to try to cache the macro expansion results to not
102.
by epage 2y ago
> I dislike clap too, it requires too much work to configure it in a sensible way (sensible being defined as working like most unix utilities have worked for the entire time I've used them), it comes with very "modern" def
103.
by epage 2y ago
Context: maintainer of clap, a Cargo team member Regarding the CLI parser > This will take in our arguments (from something like std::env::args) and return our matches, or an error. `std::env::args` will panic on non-UTF8 content, like a
104.
by epage 2y ago
Really feel that this is a missing area in CI today and looking forward to what codspeed and https://bencher.dev/ are able to create. Unfortunately, I'm not using either atm. Last I looked at them: - codspeed's R
105.
by epage 2y ago
> If everything you provide is at best a no-op and at worst a negative, and there's never an upside to it, stop providing. Write much, but say nothing. One of my best managers would help collect unofficial feedback and give it to us
106.
by epage 2y ago
Does `uv tool` fit the bill? https://docs.astral.sh/uv/concepts/tools/ From https://astral.sh/blog/uv-unified-python-packaging > Tool management: `uv tool install` and `uv tool` run (
107.
by epage 2y ago
> Pfff Now I want a language named that.
108.
by epage 2y ago
> Sandboxing against malicious crates is an out-of-scope problem. You can't do this at the language level; you need some combination of a verifier and runtime sandbox. WebAssembly components are a much more likely solution here. But
109.
by epage 2y ago
RE: Rust's pacing I've had a lot of talks with my management about that. For context, I'm on the Cargo team and have authored 11 RFCs (10 approved, 1 pending). I feel like a lot of the pacing feels slow because: - As the pro
110.
by epage 2y ago
The way jenkins did it is they took the job name and hashed that. This gives you good staggering while still being consistent from run to run (compared to using a random number). This does mean it is immutable, not just at construction bu
111.
by epage 2y ago
After working with Jenkins which has "hashed value" support for automatic staggering of jobs, I think its essential in any cron syntax evaluater.
112.
by epage 2y ago
Why would users need to be an expert in them?
113.
by epage 2y ago
In Rust, it is frowned upon to pin to an exact version. We do encourage people to specify what semver version range will work. We don't have great support for depending on and verifying multiple-major version ranges when a library brok
114.
by epage 2y ago
We want to make our software available to any system without every library maintainer being a packaging expert in every system. The user experience is much better when working within tkese packaging systems. You can control versions of soft
115.
by epage 2y ago
Real world benchmarks also wouldn't be great because they would be showing how well it works in someone else's program, rather than yours. This at least gives you an idea of what the relative cost of different operations are so yo
116.
by epage 2y ago
Also, smol_str was removed from the comparison because matklad, the author of smol_str, suggests ecow > I’d rather say the opposite: users of those crates should switch to ecow. It is exactly what smol_str would have been, if it were a p
117.
by epage 2y ago
> To the extent there is an exception, testing-only code may be. Testing-only code has very different constraints than production code anyhow. Even then, though, I still find that refactoring problem arises, and test code needs to be ref
118.
by epage 2y ago
As someone who was advocating for a similar warning in Rust (finally added to clippy in 1.78), I'm glad to see this improvement in `go vet` > The go vet subcommand now includes the stdversion analyzer, which flags references to symb
119.
by epage 2y ago
At least for servo, it started as a research project. I imagine a lot of time was spent trying out ideas for WebRender or parallel CSS (two parts that made it into Firefox). I also assume starting a browser i easier than finishing a browser
120.
by epage 2y ago
That still interferes with `git bisect`. Make the test pass in history but then make it fail in your working directory and work to get it to pass before committing.

More ›