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

Newsletter 13: A little section about rspirv-reflect #241

Closed
wants to merge 3 commits into from

Conversation

Jasper-Bekkers
Copy link
Contributor

As mentioned in #232, I wrote a small section on rspirv-reflect.

Copy link
Collaborator

@17cupsofcoffee 17cupsofcoffee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The general content of this PR looks good, but according to the tracking issue it's generally preferred to write in third person (i.e "Traverse Research have created rspirv-reflect"), to keep a consistent tone between sections. Could you tweak this to match that guideline? Happy to approve this other than that one little nitpick :)

@ozkriff ozkriff mentioned this pull request Sep 2, 2020
53 tasks
@Jasper-Bekkers
Copy link
Contributor Author

Thanks for the feedback @17cupsofcoffee, does conform to the guidelines better?

Copy link
Collaborator

@17cupsofcoffee 17cupsofcoffee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, looks better now 👍 Just a few more tweaks needed (mainly just to make the CI build happy), but will approve in advance.

![Traverse Research banner](traverse-research-banner.png)

[Traverse Research] has created the [rspirv-reflect] library to replace
our very basic use-case of the existing [spirv-reflect-rs] / [spirv-reflect]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
our very basic use-case of the existing [spirv-reflect-rs] / [spirv-reflect]
their very basic use-case of the existing [spirv-reflect-rs] / [spirv-reflect]

of writing) and it also supports all the new shader stages (both ray tracing
and mesh/task shaders) as well as the existing ones.

Traverse Research wanted to reduce their reliance on C and C++ unsafe
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Traverse Research wanted to reduce their reliance on C and C++ unsafe
Traverse Research wanted to reduce their reliance on C and C++ unsafe

and mesh/task shaders) as well as the existing ones.

Traverse Research wanted to reduce their reliance on C and C++ unsafe
libraries and at the same time we needed to support newer features that were
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
libraries and at the same time we needed to support newer features that were
libraries and at the same time we needed to support newer features that were


Traverse Research wanted to reduce their reliance on C and C++ unsafe
libraries and at the same time we needed to support newer features that were
slow to become available in the existing `spirv-reflect` library. The primary
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
slow to become available in the existing `spirv-reflect` library. The primary
slow to become available in the existing `spirv-reflect` library. The primary

Traverse Research wanted to reduce their reliance on C and C++ unsafe
libraries and at the same time we needed to support newer features that were
slow to become available in the existing `spirv-reflect` library. The primary
use-case for this library is in conjecture with the Rust wrapper around the
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
use-case for this library is in conjecture with the Rust wrapper around the
use-case for this library is in conjecture with the Rust wrapper around the

libraries and at the same time we needed to support newer features that were
slow to become available in the existing `spirv-reflect` library. The primary
use-case for this library is in conjecture with the Rust wrapper around the
DirectX Shader Compiler ([dxc]), called [hassle-rs] that Traverse Research
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
DirectX Shader Compiler ([dxc]), called [hassle-rs] that Traverse Research
DirectX Shader Compiler ([dxc]), called [hassle-rs] that Traverse Research

@ozkriff
Copy link
Member

ozkriff commented Sep 6, 2020

Thanks for the PR!

Merged manually (a68fb5f) as I don't have write permission to the PR's branch.

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.

3 participants