Skip to content
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.

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

Closed
litherum opened this issue Oct 14, 2018 · 6 comments
Closed

Comments

@litherum
Copy link
Contributor

Migrated from https://bugs.webkit.org/show_bug.cgi?id=177089:

At 2017-09-18T17:47:05Z, mmaxfield@apple.com wrote:
Add a section in WSL's documentation about how API objects and WSL interact

@litherum
Copy link
Contributor Author

At 2017-09-18T17:54:24Z, mmaxfield@apple.com wrote:
Created attachment 321109
Patch

@litherum
Copy link
Contributor Author

At 2017-09-18T18:17:13Z, mmaxfield@apple.com wrote:
Created attachment 321114
Patch

@litherum
Copy link
Contributor Author

At 2017-09-18T18:24:58Z, fpizlo@apple.com wrote:
Comment on attachment 321114
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?

@litherum
Copy link
Contributor Author

At 2017-09-18T20:42:01Z, mmaxfield@apple.com wrote:
Created attachment 321125
Patch

@litherum
Copy link
Contributor Author

At 2017-09-18T21:04:14Z, mmaxfield@apple.com wrote:
Committed r222179: http://trac.webkit.org/changeset/222179

@litherum
Copy link
Contributor Author

At 2017-09-27T19:24:51Z, webkit-bug-importer@group.apple.com wrote:
rdar://problem/34693222

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant