| Age | Commit message (Collapse) | Author |
|
Designed to work for both value types as well as ref/ptr/buffer types
Co-authored-by: Yong He <yonghe@outlook.com>
|
|
* Tuple swizzling and element access.
* Update proposal status.
* Cleanup.
* Fix merrge error.
* Address review.
|
|
* Variadic Generics Part 2: IR lowering and specialization.
* Update design doc status.
* Update design doc.
* Resolve review comments.
|
|
* Design proposal: IFunc interface.
* fix code error.
|
|
* Design proposal for Tuple types.
* formatting.
|
|
|
|
* Design proposal for variadic generics
* Update IR lowering section.
* fix typo.
* Fix error.
* Fix typos.
* fix typos.
* typo fix.
* update reviewers.
* update implementation info.
* update implementation info.
* update pr link.
* rewording.
* more rewording.
* grammar fix.
|
|
This is intended to be a starting-point proposal/RFC document that will
be discussed and iterated on to arrive at a POR that we can then use
to create multiple bite-sized issues from.
Co-authored-by: Yong He <yonghe@outlook.com>
|
|
Co-authored-by: Yong He <yonghe@outlook.com>
|
|
Bug: 4511
Author: Shannon Woods
|
|
* #include an absolute path didn't work - because paths were taken to always be relative.
* WIP artifact container format.
* WIP Artifact/shader cache document.
* Some more thoughts around caching system.
* Small improvements around source hash.
* More improvements to container discussion.
* Discussions about naming and combining options.
* Small fixes to container format doc.
* Small improvements around container doc.
* Some more improvements to container doc.
* First effort around API and container format.
* More improvements around container doc.
* First stab at a proposed approach.
* Fix some typos.
* Some other small improvements.
|
|
Checking in more in-progress proposals in the hopes of sparking discussion and/or guiding future implementation work.
|
|
This change adds a `docs/proposals/` directory to give us a place to iterate on proposals for language/compiler features that are a bit too large to handle as issues.
The first proposal I'm checking in here is a sketch of what our built-in numeric interfaces might want to look like.
I do not propose that the design in the document is perfect or even *finished*.
The goal here is to get things checked into source control to foster subsequent discussion and iteration.
|