Closed egorpugin closed 7 years ago
I can't reproduce this. In a VS2017 x86-native tools window:
C:\Users\cacarter\Desktop>git clone https://github.com/Microsoft/Range-V3-VS2015 Cloning into 'Range-V3-VS2015'... remote: Counting objects: 20237, done. remote: Compressing objects: 100% (3877/3877), done. remote: Total 20237 (delta 2850), reused 0 (delta 0), pack-reused 16110 Receiving objects: 100% (20237/20237), 6.66 MiB | 9.16 MiB/s, done. Resolving deltas: 100% (14811/14811), done. C:\Users\cacarter\Desktop>type repro.cpp #include <range/v3/all.hpp> int main() {} C:\Users\cacarter\Desktop>cl /EHsc /I Range-V3-VS2015\include repro.cpp Microsoft (R) C/C++ Optimizing Compiler Version 19.10.25017 for x86 Copyright (C) Microsoft Corporation. All rights reserved. repro.cpp Microsoft (R) Incremental Linker Version 14.10.25017.0 Copyright (C) Microsoft Corporation. All rights reserved. /out:repro.exe repro.obj
Are you certain you are including the Range-V3-VS2015 headers, and not some other copy of e.g. the upstream range-v3 headers?
It seems I tried to use 0.2.1 tag instead of master. Aren't tags should work? Or only master branch is fine?
Sorry, closing this.
No need to apologize, that's totally my mistake. Those tags are from upstream range-v3, and should not even be in this repo so as to avoid exactly this kind of confusion. I've removed these upstream version tags to avoid recurrence. Thanks for the report ;)
#include <range/v3/all.hpp>
gives