Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is "unique names" enough? #1633

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions Environments.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -59,10 +59,12 @@ The `env_` functions in rlang are designed to work with the pipe: all take an en

## Environment basics {#env-basics}

Generally, an environment is similar to a named list, with four important exceptions:
Generally, an environment is similar to a named list, with five important exceptions:

* Every name must be unique.

* All elements must be binded to a name.

* The names in an environment are not ordered.

* An environment has a parent.
Expand Down Expand Up @@ -896,7 +898,7 @@ As well as powering scoping, environments are also useful data structures in the

## Quiz answers {#env-answers}

1. There are four ways: every object in an environment must have a name;
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even if my alterations are not implemented, this must be changed to be consistent with #734

1. There are five ways: every name must be unique; every element in an environment must be binded to a name;
order doesn't matter; environments have parents; environments have
reference semantics.

Expand Down