Movatterモバイル変換


[0]ホーム

URL:


  1. Web
  2. JavaScript
  3. Reference
  4. Statements and declarations
  5. function*

function*

Baseline Widely available

This feature is well established and works across many devices and browser versions. It’s been available across browsers since ⁨September 2016⁩.

Thefunction* declaration creates abinding of a new generator function to a given name. A generator function can be exited and later re-entered, with its context (variablebindings) saved across re-entrances.

You can also define generator functions using thefunction* expression.

Try it

function* generator(i) {  yield i;  yield i + 10;}const gen = generator(10);console.log(gen.next().value);// Expected output: 10console.log(gen.next().value);// Expected output: 20

Syntax

js
function* name(param0) {  statements}function* name(param0, param1) {  statements}function* name(param0, param1, /* …, */ paramN) {  statements}

Note:Generator functions do not have arrow function counterparts.

Note:function and* are separate tokens, so they can be separated bywhitespace or line terminators.

Parameters

name

The function name.

paramOptional

The name of a formal parameter for the function. For the parameters' syntax, see theFunctions reference.

statementsOptional

The statements comprising the body of the function.

Description

Afunction* declaration creates aGeneratorFunction object. Each time a generator function is called, it returns a newGenerator object, which conforms to theiterator protocol. The generator function's execution issuspended at some place, which is initially at the very beginning of the function body. The generator function can be called multiple times to create multiple generators simultaneously; every generator maintains its ownexecution context of the generator function and can be stepped independently.

The generator allows bidirectional control flow: control flow can transfer between the generator function (callee) and its caller as many times as both parties wish to. Control flow can go from the caller to the callee by calling the generator's methods:next(),throw(), andreturn(). Control flow can go from the callee to the caller by exiting the function as normal usingreturn orthrow or execution all statements, or by using theyield andyield* expressions.

When the generator'snext() method is called, the generator function's body is executed until one of the following:

  • Ayield expression. In this case, thenext() method returns an object with avalue property containing the yielded value and adone property that is alwaysfalse. The next timenext() is called, theyield expression evaluates to the value passed tonext().
  • Ayield*, delegating to another iterator. In this case, this call and any future calls tonext() on the generator is the same as callingnext() on the delegated iterator, until the delegated iterator is finished.
  • Areturn statement (that is not intercepted by atry...catch...finally), or the end of the control flow which implicitly meansreturn undefined. In this case, the generator is finished, and thenext() method returns an object with avalue property containing the returned value and adone property that is alwaystrue. Any furthernext() calls have no effect and always return{ value: undefined, done: true }.
  • An error thrown inside the function, either via athrow statement or an unhandled exception. Thenext() method throws that error, and the generator is finished. Any furthernext() calls have no effect and always return{ value: undefined, done: true }.

When the generator'sthrow() method is called, it acts as if athrow statement is inserted in the generator's body at the current suspended position. Similarly, when the generator'sreturn() method is called, it acts as if areturn statement is inserted in the generator's body at the current suspended position. Both methods usually finish the generator, unless the generator function catches the completion viatry...catch...finally.

Generators used to be a paradigm for asynchronous programming, avoidingCallback Hell by achievingInversion of Control. Nowadays, this use case is solved with the simplerasync functions model and thePromise object. However, generators are still useful for many other tasks, such as definingiterators in a straightforward way.

function* declarations behave similar tofunction declarations — they arehoisted to the top of their scope and can be called anywhere in their scope, and they can be redeclared only in certain contexts.

Examples

Basic example

js
function* idMaker() {  let index = 0;  while (true) {    yield index++;  }}const gen = idMaker();console.log(gen.next().value); // 0console.log(gen.next().value); // 1console.log(gen.next().value); // 2console.log(gen.next().value); // 3// …

Example with yield*

js
function* anotherGenerator(i) {  yield i + 1;  yield i + 2;  yield i + 3;}function* generator(i) {  yield i;  yield* anotherGenerator(i);  yield i + 10;}const gen = generator(10);console.log(gen.next().value); // 10console.log(gen.next().value); // 11console.log(gen.next().value); // 12console.log(gen.next().value); // 13console.log(gen.next().value); // 20

Passing arguments into Generators

js
function* logGenerator() {  console.log(0);  console.log(1, yield);  console.log(2, yield);  console.log(3, yield);}const gen = logGenerator();// the first call of next executes from the start of the function// until the first yield statementgen.next(); // 0gen.next("pretzel"); // 1 pretzelgen.next("california"); // 2 californiagen.next("mayonnaise"); // 3 mayonnaise

Return statement in a generator

js
function* yieldAndReturn() {  yield "Y";  return "R";  yield "unreachable";}const gen = yieldAndReturn();console.log(gen.next()); // { value: "Y", done: false }console.log(gen.next()); // { value: "R", done: true }console.log(gen.next()); // { value: undefined, done: true }

Generator as an object property

js
const someObj = {  *generator() {    yield "a";    yield "b";  },};const gen = someObj.generator();console.log(gen.next()); // { value: 'a', done: false }console.log(gen.next()); // { value: 'b', done: false }console.log(gen.next()); // { value: undefined, done: true }

Generator as an object method

js
class Foo {  *generator() {    yield 1;    yield 2;    yield 3;  }}const f = new Foo();const gen = f.generator();console.log(gen.next()); // { value: 1, done: false }console.log(gen.next()); // { value: 2, done: false }console.log(gen.next()); // { value: 3, done: false }console.log(gen.next()); // { value: undefined, done: true }

Generator as a computed property

js
class Foo {  *[Symbol.iterator]() {    yield 1;    yield 2;  }}const SomeObj = {  *[Symbol.iterator]() {    yield "a";    yield "b";  },};console.log(Array.from(new Foo())); // [ 1, 2 ]console.log(Array.from(SomeObj)); // [ 'a', 'b' ]

Generators are not constructable

js
function* f() {}const obj = new f(); // throws "TypeError: f is not a constructor

Generator example

js
function* powers(n) {  // Endless loop to generate  for (let current = n; ; current *= n) {    yield current;  }}for (const power of powers(2)) {  // Controlling generator  if (power > 32) {    break;  }  console.log(power);  // 2  // 4  // 8  // 16  // 32}

Specifications

Specification
ECMAScript® 2026 Language Specification
# sec-generator-function-definitions

Browser compatibility

See also

Help improve MDN

Learn how to contribute

This page was last modified on byMDN contributors.


[8]ページ先頭

©2009-2025 Movatter.jp