Appendix on memory usage

[beta-ziliani]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 66fe790

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ggiraldez]

Left some suggestions.

[alcuadrado]

I like this guide. It's clear, and the suggestion isn't resorting to manual memory management.

[OmarTawfik]

I think there is a difference between the title Considerations on memory usage and the slug slang-memory-management. I suggest consolidating it here + index.md + NAVIGATION.md above:

Suggested change

	# 9.2. Considerations on memory usage
	# 9.2. Slang Memory Management

[OmarTawfik]

Suggested change

JavaScript engines distinguish between the memory space that contains JavaScript objects, called _internal memory_ or _heap space_, and the space used for Wasm components, called _external memory_. The Slang objects that you interact with reside in internal memory. However, a Slang object, such as a `Cursor`, holds a _handle_ to a Wasm component that manages a corresponding resource in the Rust implementation. In the case of a `Cursor`, that resource contains among other things _a reference to the entire parsing tree_. Therefore, an instance of the `Cursor` class in JavaScript is lightweight in terms of internal memory as it only contains the handle number. But it is associated with a significant amount of external memory—the actual cursor in Wasm-land.

JavaScript engines distinguish between the memory space that contains JavaScript objects, called _internal memory_ or _heap space_, and the space used for Wasm components, called _external memory_. The Slang objects that you interact with reside in internal memory. However, a Slang object, such as a `Cursor`, holds a _handle_ to a Wasm component that manages a corresponding resource in the Rust implementation. In the case of a `Cursor`, that resource contains among other things _a reference to the entire parsing tree_. Therefore, an instance of the `Cursor` class in JavaScript is lightweight in terms of internal memory as it only contains the handle number. But it is associated with a significant amount of external memory—the actual cursor+tree in Wasm-land.

[OmarTawfik]

Suggested change

	In an interactive environment, such as a browser, it should not be necessary to add such a pause, as the engine has several opportunities to perform cleanup while waiting for user input.
	In an interactive environment, such as an IDE or a browser, it should not be necessary to add such a pause, as the engine has several opportunities to perform cleanup while waiting for user input.

[OmarTawfik]

Love this. Left a couple of suggestions.