epage

6 ms·

1.
by epage 11d ago
Most of these global env vars started somewhere. That said, at least for cargo, there will also be a `term` config field for it.
2.
by epage 11d ago
While this is using ariadne for rendering, for annotate-snippets (the renderer for rustc) there is active work for a screen reader mode. This is being tracked at https://github.com/rust-lang/annotate-snippets-rs/is
3.
by epage 2mo ago
We are trading away disk space for faster builds. We could make them faster in some cases by using even more... On the other hand, it would be good to garbage collect those caches. We are wrapping up work on a new layout for intermediate bu
4.
by epage 3mo ago
That and the existing reply are incorrect. Almost everyone has repeated the same superficial requests and design work and not dug into the problems to come up with a proposal that respectfully threads seemingly contradictory requirements (t
5.
by epage 3mo ago
An RFC was recently merged to unblock this: https://github.com/rust-lang/rfcs/pull/3963 The implementation on this has started. Something to keep in mind is https://blog.m-ou.se/rust-is-not-a-
6.
by epage 3mo ago
As a prolific PR author, I've found how I communicate has a major factor on how well and quickly people respond to PRs. I've recorded my lessons at https://epage.github.io/dev/pr-style/ .
7.
by epage 3mo ago
As a reviewer, I love type first because it sets expectations for what I'm going to look at. Similar if I'm bisecting or doing other history operations. I don't do automated changelogs or versioning but it also makes it faste
8.
by epage 4mo ago
Not having used uv but being on the Cargo team for Rust, I wish `cargo update` was `cargo lock update` because it is making our life more difficult to add a version requirement update command/mode inside of Cargo. The effort has been s
9.
by epage 5mo ago
An important part to me that gets overlooked is shared logins. Rust runs the tests of all known Rust projects in a tool called `crater`. I was analyzing a run identifying projects relying on internals of Cargo and opening issues. When makin
10.
by epage 6mo ago
I appreciate you recognize there is still a reason for grouping commits into mergeable units (PRs). Some go too far and only want every commit to be independent. I also appreciate the ordering. In my projects, we put an extra focus on tests
11.
by epage 6mo ago
Yeah, having `cargo test` require another binary like `uv` is not idiomatic. 99% of the time, I should be able to walk up to a Rust project and run `cargo test` and it should just work.
12.
by epage 7mo ago
Really interested in this for cargo/rustc. We run into issues where we need one or two more colors but all that is left after going for the basic semantic colors is magenta (odd choice), and black and white (not safe without inspecting
13.
by epage 8mo ago
For me the issue isn't performance but bad hook updating logic. They expect hooks to be managed in isolated repos with exclusive use of tags. I have my gh action and hook in the repo of my program and it has been a source of pain to us
14.
by epage 8mo ago
In Rust, we use workspaces for - splitting up a package into smaller compilation units to speed up builds as llvm doesn't like large compilation units, e.g. I'm assuming this is why uv is split up - splitting semver concerns (easi
15.
by epage 8mo ago
> In fact, a code fence need not consist of exactly three backticks or tildes. Any number of backticks or tildes is allowed, as long as that number is at least three Unfortunately, some markdown implementations don't handle this wel
16.
by epage 8mo ago
> Use hand-written parser > > The old parser was written with winnow which is a parser combinator library. While it’s easy to create a parser with parser combinators, it’s generally slower than a hand-written parser, so the first s
17.
by epage 8mo ago
There are a couple differen things going on - completions being aware of the subcommand - dynamic look ups for specific values - completions being aware of previous options, flags, and values A lot of completions have the first. Some have t
18.
by epage 8mo ago
As I'm not familiar with the npm ecosystem so maybe I'm misunderstanding this but it sounds like they removed support for local publishes (via a token) in favor of CI publishing using Trusted Publishing. If that is correct, I thou
19.
by epage 9mo ago
It reads naturally but I can see people getting tripped up writing this. Worse for changing existing code. Refactor in a way that removes a body? Likely forget to add a breake
20.
by epage 9mo ago
I think the switch statement design is a foot gun: defaults to fall-through when empty and break when there is a body. https://c3-lang.org/language-overview/examples/#enum-and-swi...
21.
by epage 9mo ago
> > Struct variant fields are public, limiting how you evolve the fields and types > But the whole point of thiserror style errors is to make the errors part of your public API. This is no different to having a normal struct (not e
22.
by epage 9mo ago
Take the example at https://docs.rs/thiserror/latest/thiserror/ - Struct variant fields are public, limiting how you evolve the fields and types - Struct variants need non_exhaustive - It shows using `from` o
23.
by epage 9mo ago
I think we should provide the building blocks (display, etc like derive_more) rather than a specialized version one for errors (thiserror). I also feel thiserror encourages a public error enum which to me is an anti-pattern as they are usua
24.
by epage 9mo ago
> It may have been nice to expose some reasonable defaults for code coverage measurements too. Would love built in coverage support but investigation is needed on the design ( https://github.com/rust-lang/cargo/i
25.
by epage 9mo ago
For Cargo, - synchronization operations are implicit so we need to re-resolve to confirm the lockfile is still valid. We could take some short cut but it would require re-implementing some logic - dependency resolution only uses `Cargo.toml
26.
by epage 9mo ago
TOML as a format doesn't make sense for streaming - Tables can be in any order, independent of heirarchy - keys can be dotted, creating subtables in any order On top of that, most use cases for the format are not benefitted by streamin
27.
by epage 9mo ago
Lockfiles aren't an issue. It is all the dependencies themselves.
28.
by epage 9mo ago
> uv is fast because of what it doesn’t do, not because of what language it’s written in. The standards work of PEP 518, 517, 621, and 658 made fast package management possible. Dropping eggs, pip.conf, and permissive parsing made it ach
29.
by epage 9mo ago
Is there a way to check the DRM status before purchase?
30.
TOML 1.1.0(github.com)
7 points by epage 9mo ago|0 comments

More ›