Suggestion: flip the assignment direction of generated enums to save some bits

Search Terms

enum assignment

Suggestion

Flip the assignment order

Use Cases

enums

Examples

enum Action {
  foo
  bar
  baz
  thequickbrownfoxjumpsoverthelazydog
}

currently generates:

"use strict";
var Action;
(function (Action) {
    Action[Action["foo"] = 0] = "foo";
    Action[Action["bar"] = 1] = "bar";
    Action[Action["baz"] = 2] = "baz";
    Action[Action["thequickbrownfoxjumpsoverthelazydog"] = 3] = "thequickbrownfoxjumpsoverthelazydog";
})(Action || (Action = {}));

Suggesting instead:

"use strict";
var Action;
(function (Action) {
    Action[Action[0] = "foo"] = 0;
    Action[Action[1] = "bar"] = 1;
    Action[Action[2] = "baz"] = 2;
    Action[Action[3] = "thequickbrownfoxjumpsoverthelazydog"] = 3;
})(Action || (Action = {}));

Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

Commencez par compiler l’exemple d’enum de l’issue et comparer le JavaScript actuellement généré avec l’ordre d’affectation proposé. Suivez ensuite le chemin d’émission des enums du compilateur TypeScript, puis vérifiez que les enums générés utilisent la forme proposée sans modifier le comportement à l’exécution.