<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Meta-Programming on miqu.me</title><link>https://miqu.me/blog/categories/meta-programming/</link><description>Recent content in Meta-Programming on miqu.me</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 21 May 2017 22:30:00 +0100</lastBuildDate><atom:link href="https://miqu.me/blog/categories/meta-programming/index.xml" rel="self" type="application/rss+xml"/><item><title>Automatic bridging from Swift to Objective-C using Sourcery</title><link>https://miqu.me/blog/2017/05/21/automatic-bridging-from-swift-to-objective-c-using-sourcery/</link><pubDate>Sun, 21 May 2017 22:30:00 +0100</pubDate><guid>https://miqu.me/blog/2017/05/21/automatic-bridging-from-swift-to-objective-c-using-sourcery/</guid><description>&lt;p&gt;I recently read a &lt;a href="http://blog.benjamin-encz.de/post/bridging-swift-types-to-objective-c/"&gt;great post&lt;/a&gt; by &lt;a href="https://twitter.com/benjaminencz"&gt;Benjamin Encz&lt;/a&gt; about bridging Swift to Objective-C by creating bridging types that can be exposed to the older language. I wondered if his idea can be improved and automated using meta-programming with &lt;a href="https://github.com/krzysztofzablocki/Sourcery"&gt;Sourcery&lt;/a&gt; by &lt;a href="https://twitter.com/merowing_"&gt;Krzystof Zablocki&lt;/a&gt;. The answer is a very impressive ObjC-like uppercase &lt;strong&gt;YES&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>