- Revised "Substitution Maps" chapter:
- New "Subclassing" section
- New "SIL Type Lowering" section
- New "Opaque Result Types" chapter
- Various smaller edits
New PDF will be available shortly at https://download.swift.org/docs/assets/generics.pdf.
In the Swift grammar, the top-level of a source file is a mix of three
different kinds of "items": declarations, statements, and expressions.
However, the existing parser forces all of these into declarations at
parse time, wrapping statements and expressions in TopLevelCodeDecls,
so the primary API for getting the top-level entities in source files
is based on getting declarations.
Start generalizing the representation by storing ASTNode instances at
the top level, rather than declaration pointers, updating many (but
not all!) uses of this API. The walk over declarations is a (cached)
filter to pick out all of the declarations. Existing parsed files are
unaffected (the parser still creates top-level code declarations), but
the new "macro expansion" source file kind skips creating top-level
code declarations so we get the pure parse tree. Additionally, some
generalized clients (like ASTScope lookup) will now look at the list
of items, so they'll be able to walk into statements and expressions
without the intervening TopLevelCodeDecl.
Over time, I'd like to phase out `getTopLevelDecls()` entirely,
relying on the new `getTopLevelItems()` for parsed content. We can
introduce TopLevelCodeDecls more lazily for semantic walks.
I am not sure what is wrong: the text or my understanding of upstream/downstream terminology, but it seems that nameres happens before generics, and nameres results *flow* into generics, so it must be upstream, right?
Slava Pestov
Valeriy Van
Anthony Latsis
omochimetaru
Doug Gregor
swift-ci
Alex Kladov