_content/blog/comparable: clean up useless {{raw}}
The template isn't doing anything here, we can just use HTML directly.
Change-Id: I9aef23bc6a920c57a983fa87e9147e9ea5ec4cb1
Reviewed-on: https://go-review.googlesource.com/c/website/+/469097
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Auto-Submit: Michael Pratt <mpratt@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 3523bb6..93c767a 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 {{raw "<code><</code>" }} operator.)
+enumerates all basic types with an <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 {{raw "<code><</code>" }}.
+That includes all the basic arithmetic operations, but also comparisons such as <code><</code>.
But it does not include bitwise operations such as `&` or `|`
because those operations are not defined on `float64` values.
