<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 4/6/2016 1:22 PM, Russ Bishop wrote:<br>
</div>
<blockquote
cite="mid:25759958-4502-4719-A5A4-90EC683BB74D@gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div class="">The original intent was to be available on platforms
that have an Objective-C runtime (Darwin only at the moment, I
guess in theory Windows if someone were determined enough).</div>
<div class=""><br class="">
</div>
<br class="">
<div class="">You bring up a good point; there is nothing in the
protocol that absolutely requires Objective-C, only that it
requires AnyObject be the root object type. </div>
<div class=""><br class="">
</div>
<div class="">However in some hypothetical world where we support
importing C++ types, Rust types, or JavaScript (only half
trolling) types it would be nice for this protocol to have
something tying it to the idea that we are bridging to the
Objective-C/corelibs-foundation runtime specifically.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Russ</div>
</blockquote>
<br>
Good point. I was going to suggest breaking out the protocol into a
general swift version and have an objective-c specific one refine
it, but in the case where bridging to other languages happens, those
other language specific bridging protocols wouldn't be able to
refine the generic base protocol for types that want to bridge more
than one language. I formally retract my concern :)<br>
</body>
</html>