8 Commits

Author	SHA1	Message	Date
Erik Eckstein	ab1b343dad	use new llvm::Optional API ... `getValue` -> `value` `getValueOr` -> `value_or` `hasValue` -> `has_value` `map` -> `transform` The old API will be deprecated in the rebranch. To avoid merge conflicts, use the new API already in the main branch. rdar://102362022	2022-11-21 19:44:24 +01:00
Hamish Knight	6b9bcf3935	[AST] Change DotSyntaxCallExpr to take an Argument base ... This allows us to more easily propagate inout information to it, which will become a necessity once InOutExpr is removed.	2022-08-08 15:11:00 +01:00
Hamish Knight	ee49794d0f	[AST] Introduce Argument::implicitInOut ... This will allow us to abstract away the creation of InOutExpr for bits of code synthesis.	2022-08-08 15:10:51 +01:00
Hamish Knight	5418e8d934	[AST] Remove ArgumentList::composeTupleOrParenType ... Remove a redundant bit of diagnostic logic now that we better diagnose cases where an uncallable variable is in an overload set for a mismatched apply. Tweak another bit of diagnostic logic to only apply to a single arg/param case, as that seems to be what it's meant for.	2022-07-26 12:51:54 +01:00
Pavel Yaskevich	49b181136b	[AST] Augment ArgumentList::createImplicit to accept first trailing closure index	2022-02-03 19:41:00 -08:00
Xi Ge	03c76bd32d	sema: diagnose passing a non-constant value into a constant parameter	2021-11-22 11:52:57 -08:00
Hamish Knight	3e28bbbd2c	Update for review feedback ... - Remove OriginalArguments in favor of storing the pre-rewritten argument list, which simplifies things nicely - Adopt llvm::indexed_accessor_iterator	2021-09-01 18:40:29 +01:00
Hamish Knight	7c7c5319cf	[AST] Introduce ArgumentList ... Introduce the ArgumentList type, which represents a set of call arguments for a function or subscript. This will supersede the use of tuple and paren exprs as argument lists.	2021-09-01 18:40:23 +01:00