clarify wording of unresolved metasized question

rust-lang · Dec 2, 2024 · 462d016 · 462d016
1 parent 9fd3dff
commit 462d016
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/text/3729-sized-hierarchy.md b/text/3729-sized-hierarchy.md
@@ -1663,7 +1663,8 @@ longer relevant][zulip_issue_regions_too_simplistic].
   - Alternatively, described in [*Adding `?ValueSized`*][adding-valuesized], existing
     relaxed bounds syntax could be used, where a desired bound is written as opting out
     of the next strictest.
-- Should `MetaSized` be introduced?
+- Should `MetaSized` be introduced? If so, in addition to `ValueSized` or as an alternative
+  to `ValueSized`?
   - All existing types currently determine their size based on metadata, so this
     matches existing semantics.
   - Motivations for `MetaSized` are described in the [*What about `MetaSized` instead