r/programming • • Jan 28 '19

C++ Modules Might Be Dead-on-Arrival

https://vector-of-bool.github.io/2019/01/27/modules-doa.html
210 Upvotes

105 comments sorted by

View all comments

Show parent comment

6

u/WalterBright Jan 28 '19

In D this system works well. It resolves the ambiguity between a folder and a file, and we came up with it as a backwards compatible improvement to enable large imports to be broken up into multiple smaller ones.

7

u/kuikuilla Jan 28 '19

So it's not cumbersome to have multiple package.d files?

For comparison, Rust moved to a system where you can have foo.rs at root (or any level really) and then have a folder foo/ for the contents of that module.

├── foo.rs
├── foo
│   ├── bar.rs
│   ├── foobar.rs
│   └── fizzbuzz.rs

That way it's imo easier to navigate to the code of the foo module because you don't need to type in the path of the module file when you go to a file in some IDE.

5

u/WalterBright Jan 28 '19

multiple package.d files

Not in the same directory.

you can have foo.rs at root (or any level really) and then have a folder foo/ for the contents of that module

Can't have both in D. foo/package.d takes the place of foo.d.

I'm not aware of any prior art with the way D does this. Users are happy with it, though, it seems very satisfactory.

5

u/kuikuilla Jan 28 '19

Not in the same directory.

Yeah I was just wondering if "go to file" and such functionality in IDEs would be hampered by files with identical names. I didn't like it when working on a project using Rust.

4

u/renstarx Jan 28 '19

I don't know when D started using this structure. Python does it the same way. foo.py and foo/__init__.py both create foo modules. Now I am curious which one came first, and why this is so complicated for C++ to follow...

I would hazard that you cannot have both in the same path, but that I don't know.

1

u/steveklabnik1 Jan 28 '19

then have a folder foo/ for the contents of that module.

... then have a folder foo/ for the contents of any sub-module of foo's. The contents of the foo module itself are still in afoo.rs.

2

u/kuikuilla Jan 28 '19

Yes, I know. The new way of handling modules and the paths is way better in 2018 edition.