epage

7 ms·

31.
TOML 1.1.0(github.com)
7 points by epage 10mo ago|0 comments
32.
by epage 10mo ago
This is a Rust port of the Ruby implementation which was popularized by Jekyll, so it just does whatever was done in the Ruby implementation. For an overview of liquid itself, see https://shopify.github.io/liquid/
33.
by epage 10mo ago
Looks like this does compile time templating. There are reasons to explore using those over runtime templating but they don't cover all of the use cases.
34.
by epage 10mo ago
Huh, of all of my projects, I never expected this to make it to HN. Not the original author but the maintainer, so ask away. Unfortunately, I've not had as much time to devote to this for a while. There are also a lot of weird cases
35.
by epage 11mo ago
Pulling over my reddit comment > Providing a mechanism to manually disable individual default features when specifying a dependency We want this on the Cargo team; somebody just needs to do the design work, see https://github.
36.
by epage 11mo ago
I am very much a fan of codegen by generating code and saving it to disk and advocate for it in place of `build.rs` wherever possible. Unsure what the path forward for doing that for proc-macros would look like. There is talk of proc-macr
37.
by epage 11mo ago
For more string types, see https://github.com/rosetta-rs/string-rosetta-rs
38.
by epage 11mo ago
> Build times > I'm surprised I didn't see any advice about skipping proc macros or Serde for faster compile times. A more comprehensive document on build times is at https://corrode.dev/blog/tips-for-fa
39.
by epage 11mo ago
> It does this using (mostly) standard features built-in to the terminal and shell (a custom DCS): you can read their explanation here. It's possible to do this less invasively using OSC 133 escape codes; I'm not sure why Warp
40.
by epage 11mo ago
Good luck if you need cross-platform `requirements.txt` files.
41.
by epage 11mo ago
I kind of like it as it shifts the focus from syntax to logic. In futherance of that framing, some changes I'd include - make all literals the same color - make uses of defined items colored as a lighter color of the definition - still
42.
by epage 1y ago
Keep in mind the rule of thumb that a employee costs twice their salary, so that would be a 206k/year salary. Generous for some, low for others. The salary spread in the US is crazy.
43.
by epage 1y ago
I'd guess that in 99% of cases, if the borrow checker is a problem for you in Rust then you are likely not ready yet for C or Zig, particularly when you need to work in a team where mainatainability by others is critical. There are som
44.
by epage 1y ago
> You only build the world occasionally Unless a shared dependency gets updated, RUSTFLAGS changes, a different feature gets activated in a shared dependency, etc. If Cargo had something like binary packages, it means they would be opaqu
45.
by epage 1y ago
I talked a bit about this at the Rust All Hands back in May. A lot of Rust packages that people ust are setup more like header-only libraries. We're starting to see more large libraries that better fit the model of binary libraries, li
46.
by epage 1y ago
While I agree about not having hard and fast rules, like LoC per PR, the principles of this are very relevant. When reviewing a conglomerate commit in a PR, I have to reverse engineer how the different changes interact to figure out the int
47.
by epage 1y ago
Sorry to hear about the use of Perforce. Even the dinosaur of a company I used to work at shifted away. (granted, I know VCS like it are still good for assets)
48.
by epage 1y ago
I see stacked PRs as independent of this. PRs are a good unit of cohesion of changes, particularly changes that only make sense if later changes are also merged.
49.
by epage 1y ago
Agree with the overall sentiment but disagree with > A good rule of thumb is 300 lines of code changes - once you get above 500 lines, you're entering unreviewable territory. I've found LoC doesn't matter when you split up
50.
by epage 1y ago
This comes across as not being self-aware as to why security as laughed out of rooms: I read this as you correctly identifying some risks and said only offered the false-dichotomouy of solutions of "risk" and "no risk" w
51.
by epage 1y ago
> The problem is that sometimes library may need to pin a dependency version. We on the Cargo team have been working to educate people on the problems with pinning in Cargo.toml instead of relying on Cargo.lock > Then the library auth
52.
by epage 1y ago
I wouldn't say I'm a dependency maximalist but it not far off. Yes, shared code has costs - more general than you likely need, affecting complexity, compile times, etc - comes with risks for today (code) and the future (governace)
53.
by epage 1y ago
> Dependency hell [0] is a real thing which anyone who has worked on a large project has experienced. Projects having thousands, if not tens of thousands, of dependencies where you don’t know if they work properly, where are the bugs, yo
54.
by epage 1y ago
What was it about headers? In terms of rebuild performance in defining the interface vs implementation, there is interest in having rustc handle that automatically, see https://rust-lang.github.io/rust-project-goals/202
55.
by epage 1y ago
Fully agree. I had a section in the Cargo RFC devoted to why a first class solution is important, see https://rust-lang.github.io/rfcs/3502-cargo-script.html#firs...
56.
by epage 1y ago
There are at least workarounds for a surprising number of languages: https://dbohdan.com/scripts-with-dependencies Read up on the details of each one when proposing the design for Cargo script to see what we could learn.
57.
by epage 1y ago
As the person designing and implementing cargo script integration into cargo (there have been many third-party implementations in the past), I was both glad to see it in the wild and surprised and glad to see it called out like this! Docs a
58.
by epage 1y ago
T-lang and T-cargo still decided to add frontmatter to Rust, see https://rust-lang.github.io/rfcs/3503-frontmatter.html
59.
by epage 1y ago
What `cargo being cargo` problems are you having?
60.
by epage 1y ago
How does this compare to `cargo check --timings`? It visualizes each crate's build, shows the dependencies between them, shows when the initial compilation is done that unblocks dependents, and soon will have link information.

More ›