<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Feb 13, 2016 at 12:39 AM, Craig Cruden <span dir="ltr"><<a href="mailto:ccruden@novafore.com" target="_blank">ccruden@novafore.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">don’t understand that — I would think it would be up to the development (IDE) environment. Swift code is open-source and can be installed, without bundling (assuming the IDE can handle it). Just have to make sure that there is a source package that corresponds to a given release that could be downloaded</blockquote></div><br>That's a good point, we are post distributed version control era. </div><div class="gmail_extra"><br></div><div class="gmail_extra">If I understand your suggestion this means that each binary / framework should have in it's meta data a path leading to a git (or other) source repository and a pointer to the exact hash / tag of the commit that produced the given binary. This would allow IDE automation to clone the given repo automatically, and display the source during the debugging session. </div><div class="gmail_extra"><br></div><div class="gmail_extra">I think that this introduces a problem for developers working in environments that have no direct internet access (gov, army, labs) but work around could be implemented. </div><div class="gmail_extra"><br></div><div class="gmail_extra"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">puıɯ ʎɯ ɯoɹɟ ʇuǝs<br></div></div>
</div></div>