I don’t know if something like this has been done before, but I agree, the idea of the compile time version of the language being the same same as the runtime version, is very interesting. +1.
Matt > On Dec 20, 2015, at 21:43, Tyler Fleming Cloutier via swift-evolution > <[email protected]> wrote: > > Woah, Alejandro, thanks for posting this! That talk was super interesting, > particularly exciting at 49:48 <https://youtu.be/UTqZNujQOlA?t=49m48s>. That > was just plan cool. Jonathan Blow is quite the orthogonal thinker. > > +1 for this, or at least to evaluate how it would fit into the language! > > Tyler > > >> On Dec 8, 2015, at 12:01 PM, Alejandro Martinez via swift-evolution >> <[email protected] <mailto:[email protected]>> 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 >> <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. >> >> Blow seems like is going one step further and allowing the program to call >> the compiler as if it was a library and even he talks about allowing it to >> modify the AST, which is maybe going a little to far away. >> >> Anyway, that's the idea. Obviously is not something to be done in the near >> future. >> >> And sorry if it doesn't make any sense and I'm just making you lose your >> time. >> >> Cheers, >> >> Alejandro Martínez >> @alexito4 >> http://alejandromp.com <http://alejandromp.com/> >> >> >> >> _______________________________________________ >> 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
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
