ifc
ifc copied to clipboard
microsoft
SDK for the IFC specification at https://github.com/microsoft/ifc-spec
Hello developer, I would like to ask if there is a tool that can automatically classify IFC into LOD levels, or if you have a good idea about classifying IFC...
## Issue I am trying to print (using `ifc-printer`) the "header unit" IFCs for some standard headers (e.g., `filesystem`). These have been generated as follows: ``` cl.exe /std:c++latest /exportHeader /headerName:angle...
## Issue I am trying to print (using `ifc-printer`) the "header unit" IFCs for some standard headers (e.g., `vector`). These have been generated as follows: ``` cl.exe /std:c++latest /exportHeader /headerName:angle...
## Issue I am trying to print (using `ifc-printer`) the "header unit" IFCs for some standard headers (e.g., `vector`). These have been generated as follows: ``` cl.exe /std:c++latest /exportHeader /headerName:angle...
## Issue I have the following example: ```cpp export module hello; import std.core; export namespace hello { void say_hello(uint32_t count); } ``` which I compile as follows: ``` cl.exe /W4...
Try a minimal fix: - In `struct InvalidPartitionName`, replace member `std::string_view name` by `char[NAME_BUFFER_SIZE] name` and use a class-static `make` function to initialize the buffer - In `Reader::Reader`, replace `if...
Changing destination of `ifc-printer` after conversation in https://github.com/microsoft/ifc/pull/34#discussion_r1359293474
The contributing document suggests that contributors ought to format the code before submission, however there is no enforcement in CI. I would like to add it to the CI, however...
During the review of #30 , @menuet correctly observed there is existing code that violated Core Guidelines [E.14](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Re-exception-types). That should have been caught before it was checked in. Upon further...
Hi I closed inadvertently my previous PR https://github.com/microsoft/ifc/pull/30, probably because I force-pushed my related branch. So, I am creating another PR to focus specifically on the memory/life-time issue when catching...