Most of the problems we would like to see solved by modules are fundamentally caused by textual inclusion: lack of interface isolation, interface fragility, slow builds, ODR violations, and so on, are unintended consequences of the fact that interfaces are made visible by textually including the contents of a header file. This companion paper to (" Another take on modules", hereafter called the Atom proposal) provides a comparison of the design in that paper to the design of the Modules TS ( ), focusing on examples and concerns that have been raised with the Modules TS and showing how the design in might address them. This paper provides a comparison of the modules design in P0947R0 to the Modules TS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |