On Tue, Jul 15, 2025 at 1:06 PM The Cuthour <cuth...@gmail.com> wrote: > > > Facts > > (1) There's no header files in Java/Rust. > (2) There's cargo in Rust.
Ok, sounds like you want a language that is NOT C. Or you want to improve the standard C/C++ language. This is the wrong location to talk about doing that. > > I wish > > (1) There was no header files also in C/C++. > (2) There was cargo also in C/C++. > > > > > 2025年7月16日 3:50:19 JST、Andrew Pinski <pins...@gmail.com> より: > >On Tue, Jul 15, 2025 at 11:37 AM The Cuthour <cuth...@gmail.com> wrote: > >> I understand that GNU Make and C++ Modules address many current challenges > >> with headers and dependency management. > >> > >> But what I'm suggesting is a build+package manager tightly integrated with > >> the compiler — something like Rust's cargo, which not only handles builds > >> and dependencies, but also allows: > > > >Sounds what you want is RPM or deb? How will they interact and how > >will distro work? > > > >> > >> - No headers, no macros > > > >There is no way to do that with either C or C++. Unless you are > >suggesting everything is an enum now. > > > >> > >> - Cache-aware recompilation (template & inline function tracking) > > > >This breaks down very quickly. > > > >> > >> - Consistent ABI output per toolchain (e.g., Rust ABI, Go ABI) > > > >Huh? There is already consistent ABI output. > > > >> > >> - Per-project manifest with proper dependency/version resolution > > > >Sounds like you want to do a distro. > > > >Thanks, > >Andrew > > >
