Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fill in Overview.md #4

Merged
merged 1 commit into from
Apr 2, 2024
Merged

Fill in Overview.md #4

merged 1 commit into from
Apr 2, 2024

Conversation

fitzgen
Copy link
Collaborator

@fitzgen fitzgen commented Mar 27, 2024

This fills in Overview.md with content from the design issue, CG presentation, and subsequent discussions.

It tentatively specifies that custom page sizes must be a power of two between 1 and 64KiB. It is worth noting, however, that there is still somewhat active discussion surrounding what the exact values allowed should be. Powers of two seems like the option with the most support currently. It is also a superset of the other options so, should we decide to restrict custom page sizes to only the values 1 and 64KiB in the future, for example, it should be an easy migration. See #2 for more details.

There is a section that summarizes the discussion in #3. I think we've resolved the toolchain-related open questions we've thought of thus far, so I will go ahead and say that this commit

Fixes #3

Finally, there is a new section on binary encoding. I have not attempted to sketch this out yet. I will open a dedicated issue for discussing this subject.

This fills in `Overview.md` with content from the design issue, CG presentation,
and subsequent discussions.

It tentatively specifies that custom page sizes must be a power of two between 1
and 64KiB. It is worth noting, however, that there is still somewhat active
discussion surrounding what the exact values allowed should be. Powers of two
seems like the option with the most support currently. It is also a superset of
the other options so, should we decide to restrict custom page sizes to only the
values 1 and 64KiB in the future, for example, it should be an easy migration.
See #2 for more details.

There is a section that summarizes the discussion in
#3. I think we've
resolved the toolchain-related open questions we've thought of thus far, so I
will go ahead and say that this commit

Fixes #3

Finally, there is a new section on binary encoding. I have not attempted to
sketch this out yet. I will open a dedicated issue for discussing this subject.
@fitzgen
Copy link
Collaborator Author

fitzgen commented Mar 27, 2024

Here is the rendered Overview.md

I'll leave this PR open for a few days for folks to comment on it and provide any feedback they have before merging.

@fitzgen
Copy link
Collaborator Author

fitzgen commented Mar 27, 2024

Finally, there is a new section on binary encoding. I have not attempted to sketch this out yet. I will open a dedicated issue for discussing this subject.

Opened #5 for this discussion

@fitzgen
Copy link
Collaborator Author

fitzgen commented Apr 2, 2024

I'll leave this PR open for a few days for folks to comment on it and provide any feedback they have before merging.

Looks like there is not any substantive feedback on this overview document, so I'll go ahead and merge it now.

@fitzgen fitzgen merged commit 801758f into main Apr 2, 2024
@fitzgen fitzgen deleted the fill-in-overview branch April 2, 2024 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

What is the toolchain integration story?
2 participants