[swift-evolution] Run Swift code at compile time
griotspeak at gmail.com
Wed Dec 9 02:47:11 CST 2015
I would like to end up with something incorporating quoted terms, macros,
and compile time evaluation.
On Wed, Dec 9, 2015 at 1:10 PM, Alejandro Martinez via swift-evolution <
swift-evolution at swift.org> wrote:
> Yeah definitely nothing for Swift 3, totally understandable.
> I was just curious if it was feasible or just a simple NONO.
> Thanks for answering!
> Sent from my iPad
> > On 09 Dec 2015, at 05:26, Chris Lattner <clattner at apple.com> wrote:
> >> On Dec 8, 2015, at 12:01 PM, Alejandro Martinez via swift-evolution <
> swift-evolution at swift.org> wrote:
> >> Hi everyone,
> >> Don't take this mail as an oficial proposal but just as some food for
> thought, I wanted to talk about this to see what you think about it.
> >> I've been following the list since the "Open Source Day" and I've seen
> in many instances proposals that could have been solved by a macro system,
> being just a temporal solution since everything can't be done just now or
> being a permanent solution if that macro system existed. Some of them may
> include the thread about "code smells", automatic wrapper synthesis or
> deriving, or even the topic about forwarding calls automatically to an
> inner object.
> >> My thinking was how difficult or viable it would be to run Swift code
> from our programs at compile time. I'm not experienced enough on computer
> languages to see it. The first time that I saw this was in a video from
> Jonathan Blow (https://www.youtube.com/watch?v=UTqZNujQOlA) and it looked
> like a really good idea. It would be much better that force people to learn
> another language (the macro language) or any other kind of preprocessor,
> instead you could use all your knowledge but just at compile time. It can
> also have good usages apart form generating code, but generating data that
> can be generated and known at compile time. And allow even to improve the
> usage of the language (maybe DSL) at a library level.
> > This is something that could be very interesting! Unfortunately it is
> definitely out of scope for Swift 3.
> > -Chris
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution