<commit_before># Experiments

"Experiments" are what Ember CLI calls [Feature Toggle](https://en.wikipedia.org/wiki/Feature_toggle).

An experiment can be summarized into three different states.

## Development
During developement, we enable an experiment and guard the code path. (As well
as tests) By default, all experiments in this stage is enabled.

## Unsupported
The Ember CLI core team will evaluate each experiment before betas get released.
If the experiment is not ready, we delete the experiment from the codebase.

During development, we guard the code path like this:

```javascript
if (experiments.MODULE_UNIFICATION) {
  ...
} else {
  ...
}
```

If the experiment is not ready to progress to beta, we remove the experiment and
feature is disabled.

## Supported
Once an experiment has through the different betas, and we can confidently say
this experiment will be supported, we also need to clean up the experiment.

When the next set of beta is determined to be released, Ember CLI team reviews
all the experiments and either let them roll into betas or consider them
unsupported and disable them.<commit_msg>Updating docs<commit_after># Experiments

"Experiments" are what Ember CLI calls [Feature Toggle](https://en.wikipedia.org/wiki/Feature_toggle).

An experiment can be summarized into three different states.

## Development
During developement, we enable an experiment and guard the code path. (As well
as tests) By default, all experiments in this stage is enabled.

## Unsupported
The Ember CLI core team will evaluate each experiment before betas get released.
If the experiment is not ready, we delete the experiment from the codebase.

During development, we guard the code path like this:

```javascript
if (experiments.MODULE_UNIFICATION) {
  ...
} else {
  ...
}
```

If the experiment is not ready to progress to beta, we remove the experiment and
feature is disabled.

## Supported
Once an experiment has gone through the different stages of beta, and we can
confidently say a specific feature from an experiment will be supported, we
delete the exerpiemnt from the codebase.

When the next set of beta is determined to be released, Ember CLI team reviews
all the experiments and either let them roll into betas or consider them
unsupported and disable them.
{'fraction_non_alphanumeric': 0.05403050108932462, 'fraction_numerical': 0.0, 'mean_word_length': 4.492822966507177, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7106945', 'n_tokens_mistral': 583, 'n_tokens_neox': 562, 'n_words': 328}