Jon Brandvein
Jon Brandvein
See also bazelbuild/bazel#18391 about moving bzl_library into Bazel.
I created three blocking issues, #23855, #23856, and #23857, but only the last one was automatically added to the release blocking hotlist. I'm guessing this might be because the first...
Er, didn't mean to remove other reviewers per se, just meant I'd like to ensure Sasha makes the decision here since this concerns bzl_library.
Obsoleted by #289.
I can't pick this up right now but if someone wants to give it a shot, be my guest. You may want to check the [previous contents](https://github.com/bazelbuild/starlark/blob/6646b6abc6c724a975fa4b1a5408aa2fef48134d/WORKSPACE) of the `WORKSPACE`...
See also #292. We could define equality/truthiness of sequences to always be based on their content, and say for non-sequence iterables this may or may not hold. You'd think an...
See discussion in #318. I think `elems()`, as well as the return values of `enumerate()`, `range()`, and `zip()`, should be `Sequences`. But that doesn't necessarily mean sequences need to support...
> I think `elems()`, as well as the return values of `enumerate()`, `range()`, and `zip()`, should be Sequences. My thinking evolved a bit since I wrote that. See #29 for...
Given the decision in #29 to not use views for most builtin methods, the impact of this issue is not as big.
> Note that we cannot deeply freeze `**kwargs` Right, it would be shallow only, like how tuples are always at least shallowly immutable. > Dictionaries are normally mutable or deeply...