You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 82861a5
Browse filesBrowse the repository at this point in the historyBrowse files
Share a producer base, drop comments and build-script changes
Fold the duplicated IPropertyValue getters and IMarshal tearoff shared by
reference<T> and reference_array<T> into a reference_producer CRTP base; the
two leaves just supply storage, get_as, and create_property_value. Same codegen
and per-instance footprint as the two-template version, ~80 fewer source lines.
Per review feedback, strip the newly-added implementation comments from
base_reference_produce.h and base_string.h, and revert the build_test_all.cmd
compiler-selection helper and its README note so this PR carries only the
projection/boxing functionality.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Don't build C++/WinRT yourself - just download the latest version here: https://
13
13
14
14
## Working on the compiler
15
15
16
-
If you really want to build it yourself, the simplest way to do so is to run the `build_test_all.cmd` script in the root directory. It takes optional positional arguments: `build_test_all.cmd [platform] [configuration] [version] [clean] [compiler]`, e.g. `build_test_all.cmd x64 Debug 999.999.999.999 "" clang`. The `compiler` argument defaults to `msvc`; pass `clang` (or `clang-cl`) to build the compiler and test projects with the clang-cl toolset, matching the clang-cl leg of CI. Developers needing to work on the C++/WinRT compiler itself should go through the following steps to arrive at an efficient inner loop:
16
+
If you really want to build it yourself, the simplest way to do so is to run the `build_test_all.cmd` script in the root directory. Developers needing to work on the C++/WinRT compiler itself should go through the following steps to arrive at an efficient inner loop:
17
17
18
18
* Open a dev command prompt pointing at the root of the repo.
0 commit comments