dot-data

.data

dot-env

.env

The <code>.data</code> and <code>.env</code> pronouns make it explicit where to look up attribute
names when indexing <code>V(g)</code> or <code>E(g)</code>, i.e. the vertex or edge sequence of a
graph. These pronouns are inspired by <code>.data</code> and <code>.env</code> in <code>rlang</code> - thanks
to Michał Bojanowski for bringing these to our attention.
The rules are simple:<ul>
<li><code>.data</code> retrieves attributes from the graph whose vertex or edge sequence
is being evaluated.</li>
<li><code>.env</code> retrieves variables from the calling environment.</li>
</ul>Note that <code>.data</code> and <code>.env</code> are injected dynamically into the environment
where the indexing expressions are evaluated; you cannot get access to these
objects outside the context of an indexing expression. To avoid warnings
printed by <code>R CMD check</code> when code containing <code>.data</code> and <code>.env</code> is checked,
you can import <code>.data</code> and <code>.env</code> from <code>igraph</code> if needed. Alternatively,
you can declare them explicitly with <code><a href="/link/utils%3A%3AglobalVariables()?package=igraph&version=1.3.5" data-mini-rdoc="igraph::utils::globalVariables()">utils::globalVariables()</a></code> to silence
the warnings.

datasets

Routines for simple graphs and network analysis. It can
handle large graphs very well and provides functions for generating random
and regular graphs, graph visualization, centrality methods and much more.

Tam<c3><a1>s Nepusz

igraph

Network Analysis and Visualization

dot-data function

The <code>.data</code> and <code>.env</code> pronouns make it explicit where to look up attribute
names when indexing <code>V(g)</code> or <code>E(g)</code>, i.e. the vertex or edge sequence of a
graph. These pronouns are inspired by <code>.data</code> and <code>.env</code> in <code>rlang</code> - thanks
to Michał Bojanowski for bringing these to our attention.
The rules are simple:<ul>
<li><code>.data</code> retrieves attributes from the graph whose vertex or edge sequence
is being evaluated.</li>
<li><code>.env</code> retrieves variables from the calling environment.</li>
</ul>

Note that <code>.data</code> and <code>.env</code> are injected dynamically into the environment
where the indexing expressions are evaluated; you cannot get access to these
objects outside the context of an indexing expression. To avoid warnings
printed by <code>R CMD check</code> when code containing <code>.data</code> and <code>.env</code> is checked,
you can import <code>.data</code> and <code>.env</code> from <code>igraph</code> if needed. Alternatively,
you can declare them explicitly with <code><a href='https://rdrr.io/r/utils/globalVariables.html'>utils::globalVariables()</a></code> to silence
the warnings.

dot-data: `.data` and `.env` pronouns

Description

Arguments