docs
ifc-spec
docs | ifc-spec | |
---|---|---|
2 | 6 | |
103 | 69 | |
1.0% | - | |
9.4 | 6.0 | |
6 days ago | 7 months ago | |
HTML | TeX | |
MIT License | Creative Commons Attribution 4.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docs
-
C++ Modules: The Packaging Story
I've been using Conan for years with great success. I think you might have missed the documentation: https://docs.conan.io
-
Looking for projects to contribute to
https://github.com/conan-io/docs/compare/develop...develop2 there's 50k lines of different and the 2.0 docs got a complete rewrite.
ifc-spec
-
C++ Modules: The Packaging Story
There is a proposal for this: https://github.com/microsoft/ifc-spec
Only Microsoft implants that so far. I gather EDG (which powers IntelliSense) has been at least researching support for consuming IFC files.
I'm not aware of anyone sponsoring work in Clang or GCC to add IFC support.
-
Module interfaces for pre-built libraries
Note that like .lib files, you'll likely need to build and share different module binary module interface files (e.g. Visual Studio's .ifc) per architecture, since #ifdefs are resolved early. Otherwise (in theory), you could share the same BMI for different architectures since they are largely a symbol table/graph of the parsed code (higher level representation before optimizations).
-
With C++20, what replaces header-only libraries?
My hope is that the IFC format can be evolved (with community inputs) into something supported (but not necessarily required) by C++ compilers. I regard something like the IFC as a necessity for the C++ community to realize the full potential of modules.
-
is it still basically useless working with modules in g++-11?
Now, Gabriel Dos Reis has a CppCon 2021 talk describing a way compilers could communicate in enough detail such that IntelliSense, static analysis, etc. would work as expected. The file format for this mechanism is called IFC and here is the link to the relevant repo. I don't have any information about it being implemented in any compiler other than Microsoft's, but it would solve a lot of problems if it were available.
-
I hope this would ease C++ tooling
For those interested in the final pdf, here is a link to the latest release containing said pdf
What are some alternatives?
Fields2Cover - Robust and efficient coverage paths for autonomous agricultural vehicles. A modular and extensible Coverage Path Planning library
cpp-docs - C++ Documentation
Mudlet - ⚔️ A cross-platform, open source, and super fast MUD client with scripting in Lua
ipr - Compiler-neutral Internal Program Representation for C++
SonyHeadphonesClient - A {Windows, macOS, Linux} client recreating the functionality of the Sony Headphones app
AStarDemo - A basic A* example ported to C++/WinRT
lmms - Cross-platform music production software
ppm2png - Basic command line utility to convert PPM images (P3) into PNG
clangd - clangd language server
DataFrame - C++ DataFrame for statistical, Financial, and ML analysis -- in modern C++ using native types and contiguous memory storage
conan-center-index - Recipes for the ConanCenter repository
cxx20-modules-examples - C++20 modules examples