From e370ef802db979cd771f1fa3eace4c3af2d6ef9d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Klaim=20=28Jo=C3=ABl=20Lamotte=29?=
 <142265+Klaim@users.noreply.github.com>
Date: Tue, 21 Jan 2025 10:48:35 +0100
Subject: [PATCH] Add link to `build2` package (#143)

This is just a link to the `build2` package and also that mention makes it clear it's available there.
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index b740686..ecfc7d9 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@ Single header implementation of `std::expected` with functional-style extensions
 Clang + GCC: [![Linux Build Status](https://github.com/TartanLlama/expected/actions/workflows/cmake.yml/badge.svg)](https://github.com/TartanLlama/expected/actions/workflows/cmake.yml)
 MSVC: [![Windows Build Status](https://ci.appveyor.com/api/projects/status/k5x00xa11y3s5wsg?svg=true)](https://ci.appveyor.com/project/TartanLlama/expected)
 
-Available on [Vcpkg](https://github.com/microsoft/vcpkg/tree/master/ports/tl-expected) and [Conan](https://github.com/yipdw/conan-tl-expected).
+Available on [Vcpkg](https://github.com/microsoft/vcpkg/tree/master/ports/tl-expected), [Conan](https://github.com/yipdw/conan-tl-expected) and [`build2`](https://cppget.org/tl-expected).
 
 [`std::expected`](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0323r3.pdf) is proposed as the preferred way to represent object which will either have an expected value, or an unexpected value giving information about why something failed. Unfortunately, chaining together many computations which may fail can be verbose, as error-checking code will be mixed in with the actual programming logic. This implementation provides a number of utilities to make coding with `expected` cleaner.