Skip to content

Commit bd2ac77

Browse files
committed
new issue templates
1 parent 2e1cdf0 commit bd2ac77

5 files changed

Lines changed: 80 additions & 20 deletions

File tree

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: adt_const_params Experience Report
3+
about: Describe your experiences using `adt_const_params`
4+
title: '[adt_const_params Experience Report]: '
5+
labels: A-adt_const_params, C-experience-report
6+
assignees: ''
7+
8+
---
9+
10+
### Code description
11+
12+
Describe what you were trying to do with adt_const_params. Links to source code are always appreciated!
13+
14+
### What worked well
15+
16+
Describe what aspects of adt_const_params worked well for you.
17+
18+
### What worked less well
19+
20+
Describe what aspects of adt_const_params did not work well for you. Perhaps they were confusing, or you weren't able to get your code to compile the way you wanted? Or perhaps it was just not ergonomic.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feedback on required public fields
3+
about: Feedback on the requirement for ADTs to have fields no more private than the ADT itself
4+
title: '[Public Fields Feedback]: '
5+
labels: A-adt_const_params, C-feedback-public-fields, C-experience-report
6+
assignees: ''
7+
8+
---
9+
10+
### Code description
11+
12+
Describe what you were trying to do with adt_const_params. Links to source code are always appreciated!
13+
14+
### What worked well
15+
16+
Describe what aspects of adt_const_params worked well for you.
17+
18+
### What worked less well
19+
20+
Describe what aspects of adt_const_params did not work well for you. Perhaps they were confusing, or you weren't able to get your code to compile the way you wanted? Or perhaps it was just not ergonomic.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feedback on required const blocks
3+
about: Feedback on the requirement for Const Generic Arguments to use explicit `const` blocks when too complex
4+
title: '[Const Blocks Feedback]: '
5+
labels: A-min_generic_const_args, C-feedback-const-blocks, C-experience-report
6+
assignees: ''
7+
8+
---
9+
10+
### Code description
11+
12+
Describe what you were trying to do with mGCA/oGCA. Links to source code are always appreciated!
13+
14+
### What worked well
15+
16+
Describe what aspects of mGCA/oGCA worked well for you.
17+
18+
### What worked less well
19+
20+
Describe what aspects of mGCA/oGCA did not work well for you. Perhaps they were confusing, or you weren't able to get your code to compile the way you wanted? Or perhaps it was just not ergonomic.
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: mGCA/oGCA Experience Report
3+
about: Describe your experiences using `min_generic_const_args`/`opaque_generic_const_args`
4+
title: '[mGCA/oGCA Experience Report]: '
5+
labels: A-min_generic_const_args, C-experience-report
6+
assignees: ''
7+
8+
---
9+
10+
### Code description
11+
12+
Describe what you were trying to do with mGCA/oGCA. Links to source code are always appreciated!
13+
14+
### What worked well
15+
16+
Describe what aspects of mGCA/oGCA worked well for you.
17+
18+
### What worked less well
19+
20+
Describe what aspects of mGCA/oGCA did not work well for you. Perhaps they were confusing, or you weren't able to get your code to compile the way you wanted? Or perhaps it was just not ergonomic.

.github/ISSUE_TEMPLATE/use-case.md

Lines changed: 0 additions & 20 deletions
This file was deleted.

0 commit comments

Comments
 (0)