Starlark -> Skylark: final push for comment changes (1 of 2)
This is the final result of IntelliJ find/replace refactoring
scoped over the Blaze project, not including symbols.
Split into two parts because of the total number of files
is an unwieldy 358.
PiperOrigin-RevId: 306447566
diff --git a/site/docs/guide.html b/site/docs/guide.html
index 42dc848..62dceb3 100644
--- a/site/docs/guide.html
+++ b/site/docs/guide.html
@@ -1406,7 +1406,7 @@
<li><a href='user-manual.html#flag--html_details'><code>--html_details</code></a>
<p>
Additionally passing this option will render a more detailed execution chart and additional
- tables on the performance of built-in and user-defined Skylark functions. Beware that this
+ tables on the performance of built-in and user-defined Starlark functions. Beware that this
increases the file size and the load on the browser considerably.
</p>
</li>
diff --git a/site/docs/query.html b/site/docs/query.html
index c959d91..69749fc 100644
--- a/site/docs/query.html
+++ b/site/docs/query.html
@@ -566,7 +566,7 @@
<code>deps(foo/...)</code> is the dependency graphs whose roots are
all rules in every package beneath the <code>foo</code> directory.
Please note that 'dependencies' means only rule and file targets
- in this context, therefore the BUILD and Skylark files needed to
+ in this context, therefore the BUILD and Starlark files needed to
create these targets are not included here. For that you should use the
<a href="#buildfiles"><code>buildfiles</code></a> operator.
</p>
@@ -1089,7 +1089,7 @@
<pre>expr ::= loadfiles(<var>expr</var>)</pre>
<p>
The <code>loadfiles(<var>x</var>)</code> operator returns the set of
- Skylark files that are needed to load the packages of each target in
+ Starlark files that are needed to load the packages of each target in
set <var>x</var>. In other words, for each package, it returns the
.bzl files that are referenced from its BUILD files.
</p>
@@ -1170,7 +1170,7 @@
With this option, the representation of each target is as if it were
hand-written in the BUILD language. All variables and function calls
(e.g. glob, macros) are expanded, which is useful for seeing the effect
- of Skylark macros. Additionally, each effective rule is annotated with
+ of Starlark macros. Additionally, each effective rule is annotated with
the name of the macro (if any, see <code>generator_name</code> and
<code>generator_function</code>) that produced it.
</p>
diff --git a/site/docs/skylark/config.md b/site/docs/skylark/config.md
index 7123e8f..254cfdf 100644
--- a/site/docs/skylark/config.md
+++ b/site/docs/skylark/config.md
@@ -36,7 +36,7 @@
* [#5577](https://github.com/bazelbuild/bazel/issues/5577) - Starlark support
for custom build flags
* [#5578](https://github.com/bazelbuild/bazel/issues/5578) - Configuration
- doesn't block native to Skylark rules migration
+ doesn't block native to Starlark rules migration
## User-defined build settings
A build setting is a single piece of
diff --git a/site/docs/skylark/performance.md b/site/docs/skylark/performance.md
index a9b4d08..b5d2151 100644
--- a/site/docs/skylark/performance.md
+++ b/site/docs/skylark/performance.md
@@ -414,7 +414,7 @@
```
$ bazel $(STARTUP_FLAGS) dump --skylark_memory=$HOME/prof.gz
-> Dumping skylark heap to: /usr/local/google/home/$USER/prof.gz
+> Dumping Starlark heap to: /usr/local/google/home/$USER/prof.gz
```
Next, we use the `pprof` tool to investigate the heap. A good starting point is
diff --git a/site/docs/user-manual.html b/site/docs/user-manual.html
index 57ba491..bb8d173 100644
--- a/site/docs/user-manual.html
+++ b/site/docs/user-manual.html
@@ -1567,7 +1567,7 @@
<h4 id="flag--toolchain_resolution_debug"><code class='flag'>--toolchain_resolution_debug=false</code></h4>
<p>
Print debug information while finding toolchains for a rule. This might help
- developers of Bazel or Skylark rules with debugging failures due to missing
+ developers of Bazel or Starlark rules with debugging failures due to missing
toolchains.
</p>
@@ -2573,7 +2573,7 @@
<li><code class='flag'>--packages</code> dumps package cache content.</li>
<li><code class='flag'>--skyframe</code> dumps state of internal Bazel dependency graph.</li>
<li><code class='flag'>--rules</code> dumps rule summary for each rule and aspect class,
- including counts and action counts. This includes both native and Skylark rules.
+ including counts and action counts. This includes both native and Starlark rules.
If memory tracking is enabled, then the rules' memory consumption is also printed.</li>
<li><code class='flag'>--skylark_memory</code> dumps a
<href a=https://github.com/google/pprof>pprof</href> compatible .gz file to the specified path.
@@ -2620,7 +2620,7 @@
--host_jvm_args=-DRULE_MEMORY_TRACKER=1 \
dump --rules
- # Dump Skylark heap and analyze it with pprof
+ # Dump Starlark heap and analyze it with pprof
% bazel --host_jvm_args=-javaagent:$BAZEL/third_party/allocation_instrumenter/java-allocation-instrumenter-3.0.1.jar \
--host_jvm_args=-DRULE_MEMORY_TRACKER=1 \
dump --skylark_memory=$HOME/prof.gz
diff --git a/site/docs/workspace-log.md b/site/docs/workspace-log.md
index e25f926..15da79b 100644
--- a/site/docs/workspace-log.md
+++ b/site/docs/workspace-log.md
@@ -44,7 +44,7 @@
* Sometimes functions might be re-executed, in which case the related
events will show up in the log multiple times.
-* Workspace rules log currently only logs Skylark events. Some native rules
+* Workspace rules log currently only logs Starlark events. Some native rules
may cause non-hermetic behavior but not show up in this log. Examples of those
rules include
[maven_jar](/be/workspace.html#maven_jar).
