<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 21, 2018, at 11:34 PM, Luke Lau <<a href="mailto:luke_lau@icloud.com" class="">luke_lau@icloud.com</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div><div class=""><a href="https://summer.haskell.org/ideas.html#format-preserving-yaml" class="">https://summer.haskell.org/ideas.html#format-preserving-yaml</a></div><div class="">Would this new library aim to also use the C library behind the scenes, or would there be more interest in making a completely native Haskell version? (Do FFI calls in Haskell have any performance overhead?)</div></div></div></blockquote><div><br class=""></div><div>If it's <i class="">possible</i> to do this using the C library behind the scenes then I don't see any reason not that. That said, my understanding is that the C library doesn't support this use case, so it's likely you'd have to write a pure Haskell implementation.</div></div></body></html>