DartBot

_This comment was originally written by @seaneagan_ --- Strawman: varPositionals(required, [optional, String ...rest]) {   assert(rest is List<String>); } varNamed (required, {optional, String ...rest}) {   assert(rest is Map<Symbol, String>); } (...rest...

_This comment was originally written by adors...@gmail.com_ --- +1 for the Strawman in #­2. I like the '...' syntax, because it (1) semantically jibes for me, and (2) it echoes...

_This comment was originally written by @zoechi_ --- As it's just another sytax for a parameter of type List, why not just stay with List?

_This comment was originally written by ado...@gmail.com_ --- I'm not sure that using a 'List' parameter has the effect I'm looking for. If I used a 'List' parameter, wouldn't I...

_This comment was originally written by @zoechi_ --- I understand your request but I'm not sure if special syntax is worth this little (IMHO) gain.

_This comment was originally written by yu.asa...@gmail.com_ --- > This would make porting python code to dart much cleaner. As a user of Dart, I personally do not find it...

_This comment was originally written by ado...@gmail.com_ --- Yah, I agree that supporting varargs just for the sake of porting python code *is not* a good argument. However, I would...

_This comment was originally written by @seaneagan_ --- Is this asking for: * 2 separate optional parameters within the same declaration, one named, one positional * allowing a single optional...

_This comment was originally written by @seaneagan_ --- Sounds perfect! The only other thing I would change (also mentioned in issue dart-lang/sdk#6496) is to use = instead of : for...

_This comment was originally written by @rbishop-bah_ --- Related: Issue dart-lang/sdk#17101