Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
epage
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
151.
▲
by
epage
3y ago
> Within a feature branch, not every commit necessary passes the tests (or even builds), and that is a useful property! Here’s some ways this can be exploited: > When fixing a bug, add a failing test first, as a separate commit. That
152.
▲
by
epage
3y ago
The idea is one commit adds the test and another fixes it.
153.
▲
by
epage
3y ago
Async drop is a problematic case in Rust. Somehow grafting in linear types is one of the ideas that has been floated to solve this. There is also a subset of developers (typically those used to the control of C and/or in the extremes o
154.
▲
by
epage
3y ago
I acknowledged that in my comment. My point is it takes a lot of work to undo the damage to people's perception and that time you lose from doing so gets your community that much further behind.
155.
▲
by
epage
3y ago
You also need to take history into account - non-free compiler - GC (when Java, C#, etc already ate into that C++ segment - competing standard libraries These have been solved in different ways but diseminating that knowledge and changing p
156.
▲
TOML Test Matrix
(arp242.github.io)
2 points
by
epage
3y ago
|
0 comments
157.
▲
by
epage
3y ago
Based on the /r/rust thread, the author seemed to change the headline based on feedback to make it less clickbait-y
158.
▲
by
epage
3y ago
I know you said 4s is good but have you tried changing the linker? Number of dependencies likely won't affect incremental build times except for linking and replacing it might offer some good gains for incremental builds.
159.
▲
by
epage
3y ago
Keep in mind, this is still an experiment and is restricted to nightly, so its not configured for general use. Id expect the stabilized default to be number of cores. No idea where this effort is at but at one point they were going to use j
160.
▲
by
epage
3y ago
I'm hoping public/private dependencies RFC will help some. One idea we have for a follow up is to declare that you should get the version req for one crate from another.
161.
▲
by
epage
3y ago
I've seen too many cases where people see CI is a first-pass reviewer and wait for it. I can understand if people throw complete garbage at CI that will need to be reworked to the point it isn't worth reviewing. I've rarely
162.
▲
by
epage
3y ago
We have an RFC for this that has fairly broad support that I just need to bug some people some more so we can approve it. https://github.com/rust-lang/rfcs/pull/3243
163.
▲
by
epage
3y ago
> > "We're pretending security is not an issue." has been the feedback every time this is raised with the Cargo team. > Do you have a specific link where I can read this response, because this is not at all the respo
164.
▲
by
epage
3y ago
My preferred syntax route is a new separator in package names and the lib name gets populated by everything after it. Still doesn't solve all of the policy problems with namespacing.
165.
▲
by
epage
3y ago
Can't speak for why Zig doesn't have a problem but Rust is cursed by its success: it lowers the barrier for improvement enough to entice you to always improve it.
166.
▲
by
epage
3y ago
I find this interersting as most namespacing solutions would need the cargo team involved and I've heard nothing about this.
167.
▲
by
epage
3y ago
> It also looks like (soon) you’ll finally be able to configure global lints for a project. Until now, you had to hack your solution to keep lints consistent for projects. In Wick, we use a script to automatically update inline lint conf
168.
▲
by
epage
3y ago
All males in my family over produce muccous and have perpetual post-nasal drip leading to a frequent cough that is slowdy taking away our voices. Sudafed access would be great! I've gone to an ENT to try to reduce things but no luck so
169.
▲
by
epage
3y ago
Sounds like they'll be using the cargo variant of semver where changing the leading digit is a breaking change with a common expectation that fewer leading digits implies "better" for varying metrics of "better" (fe
170.
▲
by
epage
3y ago
I would love that as a solution as well but what it leave out compared to Cackle is abstractions. You can have some packages that abstract lower level operations into more restricted higher level ones which can give you a different surface
171.
▲
by
epage
3y ago
In cargo (Rust's primary build tool), there are two ways to pin dependencies: - `Cargo.lock`: handled implicitly so long as you check it in which, as of rust 1.74 (next release), `cargo new` will scaffold all projects this way by defau
172.
▲
by
epage
3y ago
That guidance has changed and will hit stable for 1.74 (5 weeks). For the new guidance: https://doc.rust-lang.org/nightly/cargo/faq.html#why-have-ca... See also https://blog.rust-lang.org/2023/
173.
▲
by
epage
3y ago
For a very rough comparison of parsers, see https://github.com/rosetta-rs/parse-rosetta-rs (which both includes a full json parser for each parser)
174.
▲
by
epage
3y ago
Been really tempted to integrate PAGER support into the cli library I maintain (clap which is for Rust)
175.
▲
by
epage
3y ago
These leaves off several relevant string types, including ecow which was encouraged over smol_str [0] See https://github.com/rosetta-rs/string-rosetta-rs for some more analysis. HipStr also has a decent table [1] [0]
176.
▲
by
epage
3y ago
Don't think I've benchmarked that case since thats not generally what you'll run into with a human data format. Would love to see numbers if you have them since I have no idea what they'd be. Personally performance isn&#
177.
▲
by
epage
3y ago
toml 1.1 will allow non-ascii in keys (and multi-line inline tables) See https://github.com/toml-lang/toml/blob/main/CHANGELOG.md
178.
▲
by
epage
3y ago
And we'd like to have native support for these in cargo: https://github.com/rust-lang/cargo/issues/10881
179.
▲
by
epage
3y ago
I think this covers it fairly well but wanted to clarify one item > There's a current RFC to use existing crates as namespace prefixes for projects. Thrs is not intended as a general purpose namespacing but to allow semi-open (rust
180.
▲
by
epage
3y ago
> Not sure why, but broader Rust community really loves participating in drama, and seems incapable of applying the modicum of Hanlon's Razor. This has been my frustration with it all. I quickly saw how this whole thing could have h
More ›