Jon Brandvein

Co-assigning myself to remind me to sync with you on the release/rollout process in particular.

You're talking about the `stardoc` rule? The attr/documentation says: ```starlark "out": attr.output( doc = "The (markdown) file to which documentation will be output.", mandatory = True, ), ``` This suggests...

See [update](https://github.com/bazelbuild/bazel/issues/14506#issuecomment-2023050460) in aforementioned bug. We want to do this, at least for *implicit* bool conversion.

Transferred to bazelbuild/starlark since `fail()` is a language-level construct. My view is that the inconvenient syntax in Richard's post isn't worth a new builtin symbol. Does a triple quoted string...

Moving to bazelbuild/starlark as it's a FR for a method on a universe symbol (list).

Also, does it make sense to talk about minimizing the number of copies if you're doing a non-in-place sort anyway? `sorted()` is [implemented](https://github.com/bazelbuild/bazel/blob/5a8a92489342d59ea74077174e29d8f10ac2989c/src/main/java/net/starlark/java/eval/MethodLibrary.java#L146) using Java's `Arrays.sort()`, which itself in the...

I guess what I meant by collisions was more that if you are forced to compartmentalize your fields by provider, you tend to be able to get away with shorter...

This is no longer applicable -- bazelbuild/starlark should concern the language and specification, not Bazel's implementation. But we need to update and/or move content in this repo accordingly.

> byte string literals The Python spec calls them "bytes literals", conspicuously omitting the term "string" when referring to them. I suggest we do the same. > byte string literals...

> The solution to this problem is to specify the behavior of Starlark strings in terms of an implementation-defined parameter K, which is 8 for Go and 16 for Java....