Skip to content

Commit 099650e

Browse files
joshtriplettJoshua Nelson
authored andcommitted
Expand discussion about documenting subjective requirements
1 parent 790d29c commit 099650e

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

text/0000-target-tier-policy.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -712,8 +712,10 @@ issue is labeled with a target-specific label.
712712
[future-possibilities]: #future-possibilities
713713

714714
Eventually, as more targets seek tier 1 status, we may want to document more
715-
criteria used to evaluate requirements such as "long-term viability of the
716-
target". We should also update these requirements whenever corner cases arise.
715+
criteria used to evaluate subjective requirements such as "viability and value
716+
of supporting the target". We should also update these requirements whenever
717+
corner cases arise. However, the subjective requirements should remain, to
718+
provide ample room for human judgment.
717719

718720
These requirements intentionally don't address the problem of scaling Rust to a
719721
huge volume of targets, where no one target causes a burden but all of them

0 commit comments

Comments
 (0)