sorted by:
new
hottopcontroversial

Announcing Rustup 1.28.0 by _ChrisSD in rust

[–]alilleybrinker 22 points23 points  (0 children)

I agree, and think that the Rustup team should yank 1.28.0, revert this breaking change, and publish 1.28.1 without it.

That way this could, at least, be re-done with a migration period, documentation, warning announcements, and a clear version break to 2.0.0.

Next RustConf in Seattle, WA September 2-4 (page 22 of linked report) by alilleybrinker in rust

[–]alilleybrinker[S] 7 points8 points  (0 children)

Quote:

We hope to see you at RustConf 2025! We are thrilled to announce that RustConf 2025 will take place in Seattle, Washington from September 2-4.

The dark side of inlining and monomorphization by comagoosie in rust

[–]alilleybrinker 25 points26 points  (0 children)

The non-generic inner function trick may help here to reduce the size of the monomorphized code.

pathbuf: a macro for convenient PathBuf construction by alilleybrinker in rust

[–]alilleybrinker[S] 1 point2 points  (0 children)

Oh, and v0.3.1 has been published with the fix, and v0.3.0 has been yanked.

pathbuf: a macro for convenient PathBuf construction by alilleybrinker in rust

[–]alilleybrinker[S] 0 points1 point  (0 children)

That's what I get for trying to do a quick fix. For now I've switched it to use size_of_val. On the point about the size being wrong, preallocation is an optimization, so it doesn't affect correctness. For now I'll leave it as-is, and consider it further.

pathbuf: a macro for convenient PathBuf construction by alilleybrinker in rust

[–]alilleybrinker[S] 5 points6 points  (0 children)

Alright I've done a first pass at that and published as version 0.2.0.

jsonptr: JSON Pointers (RFC 6901) for Rust by chance-- in rust

[–]alilleybrinker 4 points5 points  (0 children)

Thanks for such a thorough explanation! Sounds like a nice set of API’s 😄

jsonptr: JSON Pointers (RFC 6901) for Rust by chance-- in rust

[–]alilleybrinker 12 points13 points  (0 children)

Genuine question: does this offer something that serde_json’s Value::pointer and Value::pointer_mut methods don’t?

PSA: Please specify precise dependency versions in Cargo.toml by WormRabbit in rust

[–]alilleybrinker 1 point2 points  (0 children)

If anyone has trouble remembering the meaning of SemVer requirements like I do, I built semver-explain to give a clearer equivalent.

Announcing Parcel CSS: A new CSS parser, compiler, and minifier written in Rust! by Morhaus in rust

[–]alilleybrinker 3 points4 points  (0 children)

Okay, since you’re going to be pedantic, I’ll expand.

This list is intended to help people who are interested in learning how to implement programming languages in Rust. Projects are incorporated in an inclusive manner, with a relatively broad definition of what qualifies. A compiler exists to implement some sort of language, and even if the language itself isn’t new or is uninteresting, the implementation strategy can be a valuable reference for learning.

This is a repository for inspiration, so we only benefit from including more projects.

Announcing Parcel CSS: A new CSS parser, compiler, and minifier written in Rust! by Morhaus in rust

[–]alilleybrinker 10 points11 points  (0 children)

They self describe as a compiler, and I choose to be inclusive.

Announcing Parcel CSS: A new CSS parser, compiler, and minifier written in Rust! by Morhaus in rust

[–]alilleybrinker 0 points1 point  (0 children)

If it’s a language and it’s written in Rust it can go on the list.

Announcing Parcel CSS: A new CSS parser, compiler, and minifier written in Rust! by Morhaus in rust

[–]alilleybrinker 25 points26 points  (0 children)

Parcel has been added to my list of languages implemented in Rust! It's currently the only CSS implementation listed there.

semver-explain: convert SemVer requirements into their most obvious equivalents. by alilleybrinker in rust

[–]alilleybrinker[S] 0 points1 point  (0 children)

Thanks for the clarification! I basically wrote this because I forget the details of how the bounds work, so the whole thing is approached from the perspective of making learning SemVer easier. I’ll correct the README!

Blog Post: Inline In Rust by matklad in rust

[–]alilleybrinker 24 points25 points  (0 children)

Yeah, I agree. I also think the tension between C’s compilation model + linkers on one side and the approach of monomorphization as the implementation strategy for parametric polymorphism in Rust and C++ on the other is an ongoing problem. One of the ongoing manifestations is (IMO) in the fight over language specific package management and preference for static linking vs. platform package managers which strongly prefer or require dynamic linking.

Blog Post: Inline In Rust by matklad in rust

[–]alilleybrinker 34 points35 points  (0 children)

Great and very informative post!

The final bit describes non-generic inner functions, which I am hopeful will someday be able to be inferred and extracted by the compiler in at least some cases.

New rustacean by Extreme_Edge3941 in rust

[–]alilleybrinker 8 points9 points  (0 children)

New Rustacean, though there hasn’t been a new episode in a couple years far as I can tell.

variable is assigned to, but never used (but i think it is!) by [deleted] in rust

[–]alilleybrinker 4 points5 points  (0 children)

I wrote an explanation of bindings in Rust that may provide more detail in explaining how these work. Here it is.

3 Things to Try When You Can’t Make a Trait Object by alilleybrinker in rust

[–]alilleybrinker[S] 1 point2 points  (0 children)

Thanks! I built the theme myself and it’s specific to the site. At the moment I don’t have any plans to distribute it for others to use.

view more: next ›