Soup VS rust

Interesting to see how it works in CMake. I have been working for a long time on a build system that (originally) was my best shot at a "Build system for modules". Would be curious of your thoughts: Soup Build

Been using modules extensively for the past 2 years to write my build system (which itself is focused on using modules). Writing modules themselves has been really easy, as long as the compilers doesnt hit any issues. Working within MSVC has become a lot better in the last 6 months to the point where I rarely see issues anymore. Every time I try to switch to Clang or GCC it seems to fail on the most simple examples, but I hear GCC has made some improvements lately.

It is a tool I threw together to help debug my build system internals. It is WinUI, so windows only for now, but I hope to migrate it to MAUI so it can run cross platform.

Great to see more people interested in this area! Just finished reading the readme and I am really curious how you are finding the Clang modules support. Last time I tried to use it it was still heavily mixed up with Clang Modules and not that great with modules-ts. I have written my own very similar project and landed on MSVC as my primary compiler since it has the best Modules support I have found. I will hopefully find some time tonight to play around with the project more, but here are some quick thoughts.

I am hoping the release the Beta soon: https://github.com/SoupBuild/Soup

Great writeup. I have been thinking about the problem of dependency management within C++ for a while now. I believe that without adoption of a build system that was designed to handle dependency resolution natively with modules, we will always require fragile manual integration steps. If you are interested, I wrote a blog post on what I believe it will take to create such a build system and am actively working on an implementation.

A build system aimed at collaboration across teams, languages and platforms. Started out as a basic attempt to take advantage of C++20 Modules, but grew from there: https://github.com/SoupBuild/Soup

> There are online Rust compilers and interpreters already if you just want to rapid prototype and develop ideas in Rust

You are responding to one of the key developers of Rust early on[1], who's been working with the language for 14 years at that point.

[1] https://github.com/rust-lang/rust/graphs/contributors?from=2... and he's still #16 in commits overall today, despite almost no activity on the rust compiler since 2014.

If you haven't dipped your touch-typing fingers into Rust yet, you really owe it to yourself. Rust is a modern programming language with features that make it suitable not only for systems programming -- its original purpose, but just about any other environment, too; there are frameworks that let your build web services, web applications including user interfaces, software for embedded devices, machine learning solutions, and of course, command-line tools. Since a custom GitHub Action is essentially a command-line tool that interacts with the system through files and environment variables, Rust is perfectly suited for that as well.

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.