Feedback Thread: DIP 1036--Formatted String Tuple Literals--Community Review Round 1
aldacron at gmail.com
Tue Sep 8 10:59:58 UTC 2020
This is the feedback thread for the first round of Community
Review of DIP 1036, "Formatted String Tuple Literals".
**THIS IS NOT A DISCUSSION THREAD**
Posts in this thread must adhere to the feedback thread rules
outlined in the Reviewer Guidelines (and listed at the bottom of
That document also provides guidelines on contributing feedback
to a DIP review. Please read it before posting here. If you would
like to discuss this DIP, please do so in the discussion thread:
You can find DIP 1036 here:
The review period will end at 11:59 PM ET on September 22, or
when I make a post declaring it complete. Feedback posted to this
thread after that point may be ignored.
At the end of this review round, the DIP will be moved into the
Post-Community Round 1 state. Significant revisions resulting
from this review round may cause the DIP manager to require
another round of Community Review, otherwise the DIP will be
queued for the Final Review.
Posts in this thread that do not adhere to the following rules
will be deleted at the DIP author's discretion:
* All posts must be a direct reply to the DIP manager's initial
post, with only two exceptions:
- Any commenter may reply to their own posts to retract
feedback contained in the original post
- The DIP author may (and is encouraged to) reply to any
feedback solely to acknowledge the feedback with agreement or
disagreement (preferably with supporting reasons in the latter
* Feedback must be actionable, i.e., there must be some action
the DIP author can choose to take in response to the feedback,
such as changing details, adding new information, or even
retracting the proposal.
* Feedback related to the merits of the proposal rather than to
the contents of the DIP (e.g., "I'm against this DIP.") is
allowed in Community Review (not Final Review), but must be
backed by supporting arguments (e.g., "I'm against this DIP
because..."). The supporting arguments must be reasonable.
Obviously frivolous arguments waste everyone's time.
* Feedback should be clear and concise, preferably listed as
bullet points (those who take the time to do an in-depth review
and provide feedback in the form of answers to the questions in
this document will receive much gratitude). Information
irrelevant to the DIP or is not provided in service of clarifying
the feedback is unwelcome.
More information about the Digitalmars-d