Viewing profile — epage
epage
HN member- Joined
- Thu, Apr 30, 2009, 8:11 PM UTC
- HN karma
- 2,446
- Public activity
- 713 items
- HN profile
- View on Hacker News ↗
About epage
Recent public activity
-
comment
Comment #48936904
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.…
-
comment
Comment #48667078
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 …
-
comment
Comment #48665406
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/ru…
-
comment
Comment #48504481
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-s…
-
comment
Comment #48416345
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 change…
-
comment
Comment #48231919
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 upd…
-
comment
Comment #47942589
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 …
-
comment
Comment #47612999
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 …
-
comment
Comment #47511429
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 …
-
comment
Comment #47060276
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 ch…
-
comment
Comment #46880071
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 re…
-
comment
Comment #46740699
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 wh…
-
comment
Comment #46705941
> 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,…
-
comment
Comment #46698022
> 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 generall…
-
comment
Comment #46654445
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,…
-
comment
Comment #46531261
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 us…
-
comment
Comment #46482768
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
-
comment
Comment #46479540
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.…
-
comment
Comment #46439852
> > 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. Th…
-
comment
Comment #46416210
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_exhausti…
-
comment
Comment #46414637
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 publi…
-
comment
Comment #46407105
> 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 ( http…
-
comment
Comment #46405319
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-implement…
-
comment
Comment #46405272
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 …
-
comment
Comment #46405251
Lockfiles aren't an issue. It is all the dependencies themselves.