<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi, Yorick and Wouter.<div class=""><br class=""></div><div class="">Very sorry about the late reply. Been swamped with finishing up the end of the semester.</div><div class=""><br class=""></div><div class="">The abstract keyword is quite nice, and since I essentially want to make notations</div><div class="">these do not ever need to be unfolded. </div><div class=""><br class=""></div><div class="">So this might be a better fit for me. </div><div class=""><br class=""></div><div class="">Thanks a lot for explaining this!</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Harley</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 12, 2016, at 6:18 AM, Yorick Sijsling <<a href="mailto:yoricksijsling@gmail.com" class="">yoricksijsling@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">As Wouter says,the abstract keyword may be useful. I used it here for example: <a href="https://github.com/yoricksijsling/PiWare-prefixes/blob/master/src/PiWarePrefixes/Patterns/Fan.lagda" class="">https://github.com/yoricksijsling/PiWare-prefixes/blob/master/src/PiWarePrefixes/Patterns/Fan.lagda</a>.<div class=""><br class=""></div><div class="">The pattern i used is like this:<br class=""><br class="">fan-impl : ∀ n → Circ n n<br class="">fan-impl n = ...<br class=""><br class="">abstract<br class=""> fan : ∀ n → Circ n n<br class=""> fan n = fan-impl n<br class=""><br class=""> reveal-fan : ∀ n → fan n ≡ fan-impl n<br class=""> reveal-fan n = refl<br class=""><br class="">When the abstractly defined fan is used within a term it is treated similar to a postulated definition. The actual definition is only unfolded within the same abstract block. I can rewrite by reveal-fan to manually unfold the definition of fan, which is necessary for a few proofs. By using this pattern together with only a few proofs which used reveal-fan, i never had to see anything of the implementation. It also solved some performance issues in my case because the terms did not grow as large as before.</div><div class=""><br class=""></div><div class="">The DISPLAY pragma recognizes a pattern and displays it differently after the fact, while abstract definitions never get expanded at all.</div><div class=""><br class=""></div><div class="">Yorick</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, May 12, 2016 at 8:37 AM, Wouter Swierstra <span dir="ltr" class=""><<a href="mailto:w.s.swierstra@uu.nl" target="_blank" class="">w.s.swierstra@uu.nl</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Is there a way to tell Agda not to unfold these definitions in goals?<br class="">
<br class="">
</span>Have you tried using the abstract keyword? I seem to remember that it<br class="">
can be used prevent the definition being unfolded (but I can't seem to<br class="">
find any documentation).<br class="">
<span class="HOEnZb"><font color="#888888" class=""><br class="">
Wouter<br class="">
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br class="">
Agda mailing list<br class="">
<a href="mailto:Agda@lists.chalmers.se" class="">Agda@lists.chalmers.se</a><br class="">
<a href="https://lists.chalmers.se/mailman/listinfo/agda" rel="noreferrer" target="_blank" class="">https://lists.chalmers.se/mailman/listinfo/agda</a><br class="">
</div></div></blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></body></html>