lberki
lberki
Yeah, let's not do more work than is strictly necessary for Bazel 1.0. I rebased https://github.com/bazelbuild/rules_scala/pull/793 and I hope that'll be enough to turn Travis green.
@alexeagle why does rules_js not work? After a quick reading of the discussion thread on #10298 the only thing I see is the requirement for `--experimental_allow_unresolved_symlinks`.
Thanks! I thought that we had fixed that in the past but I apparently remembered it wrong.
We ran into this issue and the workaround we use is to embed a little bash script in the shebang line like this: `py_runtime(stub_shebang="#!/usr/bin/env -S /bin/bash -c '$0.runfiles/ $0')` (yes,...
@brandjon , I suppose we should just close this since Python 2 support is almost deprecated?
Does the performance matter in practice? I was under the impression that the look-for-every-include-under-every-include-path-entry algorithm isn't a concern for Bazel, because there aren't that many include path entries.
Does any compiler at the moment provide that functionality?
I'll defer to @brandjon here; he has much more context, my personal opinion is that this loos like a good idea, but I don't have all the information swapped into...
@comius I assume Walt is the right person to review this?
Update: it looks like there is a general feeling that this flag should be flipped and also a general feeling that no one wants to invest into doing so. If...