Design Meeting Minutes: 2025/05/27
NOTE: Please read the terms of participation (“Terms”) prior to joining the Teams meeting. You joining the Teams meeting with Microsoft indicates your acknowledgement, agreement, and consent to these Terms. If you do not agree to these Terms, please do not join the meeting.
If you intend to contribute code or other copyrightable materials (e.g. written comments, tools, documentation, etc.) to the hlsl specs repository, you are required to sign a Contributor License Agreement (CLA). For details, visit https://cla.microsoft.com.
Administrivia
- No updates
Issues
- No marked issues
PRs
Carried Forward
- [dxil] Proposal to add new debug printf dxil op
- @pow2clk and @tex3d will review this in more detail.
- [202x] Propose adding vk::SampledTexture* types
- Ready to merge.
- Add proposal for scalar layout for constant buffers
- Action Item @llvm-beanz - Move to merge.
- Introduce really rough linalg matrix proposal
- Action Item: @llvm-beanz to merge
- Rough proposal collecting thoughts on uniformity
- Action Item: @llvm-beanz to update
- New Proposal: Draft proposal to modify resource typing in HLSL
- Action item: @llvm-beanz to work with author
Current Business
- Add an initial proposal for HLSL 202x deprecations
- Needs second review
- Action Item: @pow2clk, @V-FEXrt
- Constant Buffer Contexts
- Ready for review
- Action Item: @hekota, @V-FEXrt
- Design Considerations Update
- Some concerns were raised about whether or not we should directly refernece The Zen of Python, or if we should instead codify more concrete rules ourselves.
- Some concerns were raised about the lack of specificity of the Zen of Python.
- Additional concerns were raised about Python specifically being an interpreted and very different language.
- Counter points were raised that the intent isn’t that these be hard rules, and that nothing about the Zen of Python is specific to scripting languages or dynamic typing.
- Action Item: @pow2clk plans to review in detail and provide concrete feedback on the PR.
- Additonal feedback is greatly appreciated.
- Some concerns were raised about whether or not we should directly refernece The Zen of Python, or if we should instead codify more concrete rules ourselves.
- Memory and Execuition Model
- Draft document provides three alternatives on a spectrum from full lockstep to fully indipendent threads.
- Some discussion about whether or not the code examples are or should be considered valid and it what contexts they might be.
- We need more extensive review and refinement as well as more fleshing out of the memory model.
- Action Item: @llvm-beanz to continue iterating on the proposal.