Ellie Hermaszewska
Ellie Hermaszewska
We should be able to comment `/format` on a PR to run the formatters on the changes and push the corrected code. Use something like slash-command-dispatch
- [ ] Document formatting procedure - [ ] CI checks for cpp formatting - [ ] Check that there's nothing super weird, especially around our usage of x-macros and...
- [ ] Review the two popular cmake formatters, cmake-format and gersemi - [ ] Document formatting procedure - [ ] CI checks for CMake formatting
https://github.com/github-linguist/linguist I'm pretty sure that we meet the popularity requirements by now, we'd need to open a PR which implements slang file detection (the .slang extension is unused so far...
Without any automated checks, it's an accident waiting to happen. I don't know the details, but I think that we should be able to add some shibboleth to the internal...
Hopefully will cover such topics as: - How far can we write down and specify in documentation Slang's existing type system, having a set of typing judgements for Slang programs...
```slang struct S{} func foo(s : S) -> int; let s : S = {}; let i = foo(s); ``` We should be able to infer N here as equal...
It's quite opaque, for example here: https://github.com/shader-slang/slang/pull/5243#issuecomment-2402503402
At the moment there are certain "failures" which don't fail the build, for example not having slang-llvm around mean that filecheck tests aren't run, so have no opportunity to fail....