Results 17 issues of molikto

search `[issue 7]` in code for background, or see this commit 1855e9218c7388ce1b4bf1f19d6679fcaea2324c this issue only touch the parser and elaborator, don't touch the core

good first issue

* color code name introduction, implicit name introduction and name usage, * color code keywords this will require when type checking, annotate Term.attributes, mutable field is fine!

help wanted

the idea is `define with_constructors nat = ...` will define `suc` `zero` at the same level as `nat`. currently they are used as `nat.zero`

help wanted

basically is it possible to have ``` #[repr(transparent)] pub struct Test([u32]); #[spirv(compute(threads(8, 8)))] pub fn entry( #[spirv(storage_buffer, descriptor_set = 0, binding = 0)] data: &Test, ) { } ```

t: enhancement
s: qptr may fix

try fixing https://github.com/EmbarkStudios/rust-gpu/issues/873 . context is this https://github.com/EmbarkStudios/rust-gpu/pull/690#pullrequestreview-719958024 . The tests I added still errors, but a different one compared to what I am trying to fix. But the wired...

s: waiting on author
s: qptr may fix

* warn on `inline(never)` that are not respected * inline global variables so that we can inline less functions caused by illegal arg/return type fix https://github.com/EmbarkStudios/rust-gpu/issues/847 ## tests My shader...

s: waiting on review
s: qptr may fix

### Expected Behaviour spriv-val should not fail. Looks it's because the bug mentioned here https://github.com/EmbarkStudios/rust-gpu/pull/690#pullrequestreview-719958024 . I will try to make a PR to fix it ### Example & Steps...

t: bug
s: qptr may fix