Allow top-level await in namespaces

Suggestion

🔍 Search Terms

Top, level, await, namespace, export

✅ Viability 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, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

Allow top-level await in namespaces.

Current behaviour:

// ok
await 1;

export namespace Example {
	// not ok
	await 1;
}

📃 Motivating Example

Current:

export const _keyValuePair = await idbKeyValuePair.load("name");
export namespace storage {
	export const keyValuePair = _keyValuePair;
}

💻 Use Cases

export namespace storage {
	export const keyValuePair = await idbKeyValuePair.load("name");
}

El issue no menciona archivos del repositorio, pruebas ni puntos de entrada; comienza rastreando el manejo del compilador de top-level await y los cuerpos de namespace. Usa los ejemplos de namespace proporcionados para definir la finalización: las expresiones await dentro de los namespaces deberían aceptarse sin cambiar el comportamiento existente del runtime de JavaScript.