message: Remove the README section about string incompatibilities
  Summary: I don't think we're 100% compliant everywhere, but we are mostly correct, and the underlying issue we used to link to got closed a while ago after improvements.
diff: @@ -43,7 +43,6 @@ In this section we outline where we don't comply with the [Starlark spec](https:
  * We have plenty of extensions, e.g. type annotations, recursion, top-level `for`.
  * We don't yet support later additions to Starlark, such as [floats](https://github.com/facebookexperimental/starlark-rust/issues/3) or [bytes](https://github.com/facebookexperimental/starlark-rust/issues/4).
  * We are currently limited to [32 bit integers](https://github.com/facebookexperimental/starlark-rust/issues/6). Constructing larger values will result in Starlark failing with an overflow error.
  -* Our strings are [not compliant in several ways](https://github.com/facebookexperimental/starlark-rust/issues/16), often returning code points instead of singleton strings, and have poor performance.
  * In some cases creating circular data structures may lead to stack overflows.
  ## Making a release
  