I jumped around a bit, but it seems like you can't import by any schema other than "a local file"? If that's the case, it would put this module implementation way behind the curve already, before it's even out. There are of course issues around allowing this, but for example golang has come a long way in sorting this out already (i.e "go mod" in go 1.12 and up). Importing modules directly from say github, being able to pin versions, and have them authenticated via a checksum database are all very good features that makes life for golang programmers easier. The golang people got this all wrong initially, but have managed to pivot. I hope the C++ standards people have learned from this.
Agreed, this is the duty of a package manager, not the C++ standards committee nor any implementer. One of the main purposes of C++ modules is to simplify the duty of package managers and build tools however. I suspect that cmake will be supplanted as the defacto build tool on *nix platforms by whatever module and package management tool integrates into the c++ modules ecosystem best.
Very very very excited to get this...
Amazing. Very good talk. Cannot wait.
Game changer
Wow! Ada has always had this.
Nice suits
I jumped around a bit, but it seems like you can't import by any schema other than "a local file"? If that's the case, it would put this module implementation way behind the curve already, before it's even out. There are of course issues around allowing this, but for example golang has come a long way in sorting this out already (i.e "go mod" in go 1.12 and up).
Importing modules directly from say github, being able to pin versions, and have them authenticated via a checksum database are all very good features that makes life for golang programmers easier. The golang people got this all wrong initially, but have managed to pivot. I hope the C++ standards people have learned from this.
What you describe sounds like a package manager to me.
Agreed, this is the duty of a package manager, not the C++ standards committee nor any implementer. One of the main purposes of C++ modules is to simplify the duty of package managers and build tools however. I suspect that cmake will be supplanted as the defacto build tool on *nix platforms by whatever module and package management tool integrates into the c++ modules ecosystem best.
Importing remote sources belongs to the build process, not the C++ spec. For example, when using Cmake: ExternalProject_Add
There will be a proposal to change the C++ name to Javascript++ 😂
Just kidding, haha! Very good talk, indeed!