epage

18 ms·

181.
by epage 3y ago
Huh, somehow I missed that bit on reddit. As for Discord, I tend to keep my interactions there to a minimum, so not suprised that I missed that.
182.
by epage 3y ago
> Originally the conspiracy was to move Rust towards Bazel/Buck. Never saw this part of the conversation and hope no one took my words to mean I felt that. I only expressed regret that he (a Project member and maintainer of one of t
183.
by epage 3y ago
That does not line up with the known facts at all. It sounds like people were excited by the idea of the speaker themself and different people had different thoughts on the topic and there were communication break downs around that.
184.
by epage 3y ago
To summarize the post, people quickly latched onto the idea that David was trying to sabbotage introspection to protect his empire of Rust packages which are critical to the use of macros (syn, proc-macro2) and heavy users (serde).
185.
Change in Guidance on Committing Lockfiles (Rust)(blog.rust-lang.org)
3 points by epage 3y ago|1 comments
186.
by epage 3y ago
I've been exploring local, cross-project caching for cargo and my biggest concern is users won't get enough cache hits. With maximal versions and a arbitrary set of dependencies being updated when adding a new dependency. all pro
187.
by epage 3y ago
I do know there is vague / high-level interest in this kind of approach though I expect this would require a lot of work from the compiler, especially when it comes to figuring out what traits need to be compiled. Already, rust splits
188.
by epage 3y ago
They should enable the nightly-only "auto cfg" feature to also help out e,g, https://docs.rs/clap/latest/clap/macro.command.html To enable - Add a `cfg`: https://github.com/clap-rs&#
189.
by epage 3y ago
Living in Texas, my cold showers during the summer feel amazing after a run ... for how cold they can actually get. I can stand in them indefinitely.
190.
by epage 3y ago
I disagree that what was done with good but agree with matklad [0] about basic expectations of transparency and communication when you maintain de facto standards. This is too big of an "experiment" to run in production code on t
191.
by epage 3y ago
Not Haskell style lazy but more of declarations are just another statement that aren't evaluated until those lines are executed. This means you can have function definitions inside of ifs which can be very useful for conditional progr
192.
by epage 3y ago
We're working on "scripting" support for Rust ( https://doc.rust-lang.org/nightly/cargo/reference/unstable.h... ). Currently our biggest open design issue is what syntax to use for embedding the
193.
by epage 3y ago
> Normal recumbents are also bloody dangerous I've normally been saying the opposite. Been riding a (2 wheel) recumbent for 15 years or so. I'm pretty much never going to endo. My biggest risk is falling sideways and I'
194.
by epage 3y ago
At least linear types means you'll never forget it. It also solves the problem of what to do when your destructor needs to error (e.g. closing a file). The big downside is the verbosity of covering every branch of your code with your
195.
by epage 3y ago
I appreciated the approach in https://sabrinajewson.org/blog/errors
196.
by epage 3y ago
Had to go to the link to confirm whether this was the projection language or the region language.
197.
by epage 3y ago
From cargo's changelog [0] > Automatically inherit workspace fields when running `cargo new`/`cargo init`. #12069 [1] imo I think this is a big quality of life improvement [0] https://github.com/rust-lang/c
198.
by epage 3y ago
The problem is when you are dealing with dependencies that are "vocabulary terms". These are required to be common. In Rust, one example would be serde and I'm assuming pydantic would similary apply. For Rust, these can also
199.
by epage 3y ago
I used Phab at a job and it was a complete mess. Stacked Diffs only sort-of worked, CI integration was bad, notifications were so noisy everyone tuned them out, etc. Talking with a Meta person, it sounds like Phab really needs Mercurial to
200.
by epage 3y ago
> Rumor 2: The Rust compiler is not as fast as people would like – Confirmed ! I wish there was more context to these, especially this one. For example, how much of this is perception compared to what they were used to (go?, Python?, C+
201.
by epage 3y ago
In the end, we decided the goal is to make test harnesses not special so people can choose a solution like this if they want. Personally, I feel like this does not fully cover the fixture use case.
202.
by epage 3y ago
That depends. Do you want the dynamically generated tests reported in discover? If so, then you need to assume that if you pass in the reference that it will only be used for dynamically generating tests and not for helping with skipping of
203.
by epage 3y ago
I think I bring up rstest at some point which supports similar. The downside is it is static. For example, I can't discover tests from the filesystem like trybuild does.
204.
by epage 3y ago
For me, it was slashdot to Digg to reddit...
205.
by epage 3y ago
I gave up on Ubuntu after some snap frustrations. I tried Nix but couldn't figure out how to install some software I needed (dealt with plugins). I tried Manjaro but the system was unbootable after a software update soon after install
206.
by epage 3y ago
There are some efforts for lowering the overhead and would be interesting to explore how we could further do it. First, we allow sharing `Cargo.toml` fields across the workspace since 1.64.0 [0]. In the upcoming 1.71.0, we extend this so t
207.
by epage 3y ago
> So while Go encourages having reasonably sized packages, Rust unfortunately encourages huge crates. I'm a bit confused by this as I'm used to seeing the opposite complaint, that Rust packages are too small. Maybe if there w
208.
by epage 3y ago
> - := for assignment is similar enough to what is used in math for definition, so that languages like Pascal use it I think its cppfront that is taking the approach of `:=` being a declaration with the type being inferred (ie shorthand
209.
by epage 3y ago
I feel like I'll have to read up some more to have the background to fully understand the article but one thing I wanted to point out is a difference between `fn rand_int(rand: &mut Random) -> i64` and `fn rand_int(ran: Random)
210.
by epage 3y ago
matklad, of rust-analyzer fame among many other things, wrote up their thoughts on Zig: https://matklad.github.io/2023/03/26/zig-and-rust.html I've seen some put it as "zig is good when `unsafe` hea

More ›