_content/blog/comparable: bypass < encoding
Markdown conversion converts < to &lt;, but
golang.org/x/website/cmd/golangorg TestAll rejects pages containing
&lt;. Manually override this conversion with {{raw}}.
Change-Id: I25756a52d69ac72e276741e812f8d30b9f9c5c8d
Reviewed-on: https://go-review.googlesource.com/c/website/+/469096
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Run-TryBot: Michael Pratt <mpratt@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
diff --git a/_content/blog/comparable.md b/_content/blog/comparable.md
index 8b69240..3523bb6 100644
--- a/_content/blog/comparable.md
+++ b/_content/blog/comparable.md
@@ -106,7 +106,7 @@
which accepts any `int64` or `float64` argument.
(Of course, a more realistic implementation would use a constraint that
-enumerates all basic types with an `<` operator.)
+enumerates all basic types with an {{raw "<code><</code>" }} operator.)
As an aside, because enumerating explicit types without methods is common,
a little bit of [syntactic sugar](https://en.wikipedia.org/wiki/Syntactic_sugar)
@@ -146,7 +146,7 @@
For instance, given the `min` example, in the function body any operation that is supported by
`int64` and `float64` types is permitted on values of the type parameter `P`.
-That includes all the basic arithmetic operations, but also comparisons such as `<`.
+That includes all the basic arithmetic operations, but also comparisons such as {{raw "<code><</code>" }}.
But it does not include bitwise operations such as `&` or `|`
because those operations are not defined on `float64` values.
