Skip to content

Commit a450d64

Browse files
authored
mention that omitted types cannot be emitted in phase one (#2228)
1 parent 70eb85c commit a450d64

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

working/macros/feature-specification.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,11 @@ the place where the type annotation was omitted.
8585
There are two things you can do with an `OmittedTypeAnnotation`:
8686

8787
- Pass it directly as a part of a `Code` object.
88+
- This is only allowed after phase one (the types phase). Using an omitted
89+
type in phase one is not allowed and will cause an exception.
90+
- Users should be instructed to add a type to the location where the
91+
omitted type came from in this case. It is guaranteed to be in the same
92+
file as the macro annotation, so they can always do this.
8893
- When the final augmentation library is created, the actual type that was
8994
inferred will be used (or `dynamic` if no type was inferred).
9095
- Explicitly ask to infer the type of it through the builder apis (only

0 commit comments

Comments
 (0)