| commit | 58f6611fe3151eaf5ee3993150fba305d7b0669d | [log] [tgz] |
|---|---|---|
| author | Dan Albert <danalbert@google.com> | Tue Aug 01 23:27:45 2017 +0000 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Aug 01 23:27:45 2017 +0000 |
| tree | c3d6be746f6a55910201ca405b0d1204a4f93caa | |
| parent | 8dfe66e81d38fac97b4a053873cc3022e4619092 [diff] | |
| parent | c1b94b10a13f22e951c429e056b151d340238e27 [diff] |
Merge remote-tracking branch 'aosp/upstream-master' into HEAD am: a78a14d02f am: c1b94b10a1 Change-Id: I8541109c3fb10caea0cf16eeb770753c1fc33839
The Guideline Support Library (GSL) contains functions and types that are suggested for use by the C++ Core Guidelines maintained by the Standard C++ Foundation. This repo contains Microsoft's implementation of GSL.
The library includes types like span<T>, string_span, owner<> and others.
The entire implementation is provided inline in the headers under the gsl directory. The implementation generally assumes a platform that implements C++14 support. There are specific workarounds to support MSVC 2015.
While some types have been broken out into their own headers (e.g. gsl/span), it is simplest to just include gsl/gsl and gain access to the entire library.
NOTE: We encourage contributions that improve or refine any of the types in this library as well as ports to other platforms. Please see CONTRIBUTING.md for more information about contributing.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project makes use of the Catch testing library. Please see the ThirdPartyNotices.txt file for details regarding the licensing of Catch.
The test suite that exercises GSL has been built and passes successfully on the following platforms:1)
If you successfully port GSL to another platform, we would love to hear from you. Please submit an issue to let us know. Also please consider contributing any changes that were necessary back to this project to benefit the wider community.
1) For gsl::byte to work correctly with Clang and GCC you might have to use the -fno-strict-aliasing compiler option.
To build the tests, you will require the following:
These steps assume the source code of this repository has been cloned into a directory named c:\GSL.
Create a directory to contain the build outputs for a particular architecture (we name it c:\GSL\build-x86 in this example).
cd GSL md build-x86 cd build-x86
Configure CMake to use the compiler of your choice (you can see a list by running cmake --help).
cmake -G "Visual Studio 14 2015" c:\GSL
Build the test suite (in this case, in the Debug configuration, Release is another good choice).
cmake --build . --config Debug
Run the test suite.
ctest -C Debug
All tests should pass - indicating your platform is fully supported and you are ready to use the GSL types!
As the types are entirely implemented inline in headers, there are no linking requirements.
You can copy the gsl directory into your source tree so it is available to your compiler, then include the appropriate headers in your program.
Alternatively set your compiler's include path flag to point to the GSL development folder (c:\GSL\include in the example above) or installation folder (after running the install). Eg.
MSVC++
/I c:\GSL\include
GCC/clang
-I$HOME/dev/GSL/include
Include the library using:
#include <gsl/gsl>
For Visual Studio users, the file GSL.natvis in the root directory of the repository can be added to your project if you would like more helpful visualization of GSL types in the Visual Studio debugger than would be offered by default.