> On May 31, 2016, at 12:17 PM, L Mihalkovic via swift-evolution > <[email protected]> wrote: > > well there is no macro system, and for the moment a clear statement from > chris that this is not on the table in the short term. the code in the > example looked like run-of-the-mill swift, except for the “…". so that leaves > us with swift looking code that would be executed by the compiler, but with > nothing particular to tell which parts to and which not. just a thought.
Lets be clear though: variadic generics are not in scope for Swift 3 either. I definitely don’t speak for the rest of the core team, nor have I discussed it with them… but IMO, this whole feature seems like a better fit for a macro system than it does to complicate the generics system. Unlike C++’s template system, our generics system inherently has runtime / dynamic dispatch properties, and I don’t think that shoehorning variadics into it is going to work out well. -Chris > > >> On May 31, 2016, at 7:59 PM, Austin Zheng <[email protected] >> <mailto:[email protected]>> wrote: >> >> How so? I'm interested in anything that can get us away from having to >> generating code at compile-time. >> >> On Tue, May 31, 2016 at 10:04 AM, L. Mihalkovic >> <[email protected] <mailto:[email protected]>> wrote: >> >> What's interesting about the code in the manifesto is that it looks very >> much like "..." is a runtime construct, as opposed to trying the get the >> compiler to do the heavy lifting. >> > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
