Blueprint assignments for “Ecru”
This listing shows the assignment of work for blueprints currently associated with Ecru. The drafter is responsible for getting the specification correctly written up and approved. The approver is usually the person who would sign off on the specification.
| 1 → 13 of 13 specifications | First • Previous • Next • Last |
| Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
|---|---|---|---|---|---|---|
| 5 Essential | Vats | 4 Discussion | 1 Not started | Allen Short | ||
| 1 Undefined | Expression use analysis | 3 Drafting | 0 Unknown | |||
| 1 Undefined | Unicode support | 3 Drafting | 0 Unknown | |||
| 1 Undefined | Foreign function interface | 4 Discussion | 0 Unknown | |||
| 1 Undefined | Module system | 4 Discussion | 0 Unknown | Allen Short | ||
| 1 Undefined | Guard-based auditors | 5 New | 0 Unknown | |||
| 1 Undefined | Stack traces and debugging info | 5 New | 0 Unknown | |||
| 1 Undefined | Deslotification | 5 New | 0 Unknown | |||
| 1 Undefined | Unboxing based on type information from guards | 5 New | 0 Unknown | |||
| 1 Undefined | Compile to LLVM | 5 New | 0 Unknown | |||
| 1 Undefined | Vat memory limits | 5 New | 0 Unknown | |||
| 1 Undefined | Precise GC | 5 New | 0 Unknown | |||
| 1 Undefined | Stack traces | 5 New | 0 Unknown |
| 1 → 13 of 13 specifications | First • Previous • Next • Last |
