Command-line option changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676 104.5 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676 104.6 New library followed by pre-release and build alpha- numeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Command-line option changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676 104.5 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676 104.6 New library followed by pre-release and build alpha- numeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2041 109.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2042 109.7 New library followed by pre-release and build alphanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor ver- sion 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.7 New library followed by pre-release and build al- phanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.7 New library followed by pre-release and build al- phanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.7 New library followed by pre-release and build al- phanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.7 New library followed by pre-release and build alphanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor ver- sion 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.7 New library followed by pre-release and build alphanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor ver- sion 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.7 New library followed by pre-release and build alphanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor ver- sion 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2030 108.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2030 108.7 New library followed by pre-release and build alphanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor ver- sion 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful