Bug 177089 – Add a section in WSL's documentation about how API objects and WSL interact

• Status: RESOLVED
• Resolution: FIXED
• Component: New Bugs

[Myles C. Maxfield]

Add a section in WSL's documentation about how API objects and WSL interact

[Myles C. Maxfield]

Created attachment 321109 [details]
Patch

[Myles C. Maxfield]

Created attachment 321114 [details]
Patch

[Filip Pizlo]

Comment on attachment 321114 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=321114&action=review

> Tools/WebGPUShadingLanguageRI/WSL.md:402
> +WSL is designed to be useful as both a graphics shading language and as a computation language. However, these two environments have
> +slightly different semantics.
> +
> +When using WSL as a graphics shading language, there is a distinction between *entry-points* and *non-entry-points*. Entry points are
> +top-level functions which have either the `vertex` or `fragment` keyword in front of their declaration. Entry points may not be forward
> +declared. An entry point annotated with the `vertex` keyword may not be used as a fragment shader, and an entry point annotated with the
> +`fragment` keyword may not be used as a vertex shader. No argument of an entry point may be a pointer. Entry points must not accept type arguments (also known as "generics").

For the rest of the document, I was ensuring that paragraphs were all on one text line without wrapping.

I know that's unusual, but it's intentional: the way that wordpress is configured on the webkit.org blog, newlines inside paragraphs will break the paragraph.

Can you format it the way the rest of the document does it, to make it easier to turn this into a webkit.org blog post if we want?

[Myles C. Maxfield]

Created attachment 321125 [details]
Patch

[Myles C. Maxfield]

Committed r222179: <http://trac.webkit.org/changeset/222179>

[Radar WebKit Bug Importer]

<rdar://problem/34693222>

[Myles C. Maxfield]

Migrated to https://github.com/gpuweb/WHLSL/issues/192