Make Compiler Explorer easier to find (#2100)

Our "Getting Started" section doesn't mention the Compiler Explorer as a first step.  Compiler Explorer already has the Carbon explorer installed, so it would save interested folks a lot of time if they just want to try code out before installing a lot of tools to build from scratch.

This is a repeat link of the status section, but given the title of this section ("Getting Started") it's quite possible visitors end up here before they read the status section.
This commit is contained in:
Wolff Dobson
2022-08-25 09:10:07 -07:00
committed by GitHub
parent a937d911cb
commit cb670aa6a1
+5 -2
View File
@@ -266,8 +266,11 @@ semantics onto C++ such as Rust-inspired
## Getting started
You can get started playing with Carbon by checking out the codebase and using
the Carbon explorer:
As there is no compiler yet, to try out Carbon, you can use the Carbon explorer
to interpret Carbon code and print its output. You can try it out immediately at
[compiler-explorer.com](http://carbon.compiler-explorer.com/).
To build the Carbon explorer yourself, follow these instructions:
```shell
# Install bazelisk using Homebrew.