<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">From what I see, talking about Fields, Rings, vector spaces etc... we're talking about modeling the standard library upon mathematic models / axioms (particularly algebra) and using the same terminology.<br />
<br />
Those constructions allow for a more flexible approach as one would be able to 'code theorems' on the top of the std library based on their mathematical definitions, instead of their CS oriented definitions.<br />
<br />
That's overly abstract, incredible low level and insanely powerful at the same time.<br />
<br />
Still it's an interesting concept of modeling the 'algebra' based upon those abstract structures, even if I believe the real world examples of usage would be thin.<br /></div>
<div name="messageSignatureSection"><br /></div>
<div name="messageReplySection"><br />
On Jan 16, 2017, 9:26 PM -0500, Jay Abbott via swift-evolution <swift-evolution@swift.org>, wrote:<br />
<blockquote type="cite">
<div dir="ltr">
<div>
<div>I barely understand any of this thread, so these might be silly questions, or based on a total misunderstanding the goals here, but it seems to be about: a) clever/advanced mathsy things; b) naming things; and c) the standard library... my questions are:<br />
<br />
Do specialised clever advanced mathsy libraries all work exactly the same, or do they have slightly different behaviours or conventions or semantics in different fields of study?<br />
<br />
Is the the goal here to define a common/shared sub-set of specialised maths libraries, but in the standard library? Would that be useful by itself?<br />
<br /></div>
Could it be possible that "naming things" in the standard library would trample all over possible uses in external libraries, making it harder rather than easier for specialised maths libraries to construct their interfaces in a non-confusing way?<br />
<br /></div>
</div>
<br />
<div class="gmail_quote">
<div dir="ltr">On Tue, 17 Jan 2017 at 01:39 Dave Abrahams via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br /></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="gmail_msg" />
on Mon Jan 16 2017, Xiaodi Wu <<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>> wrote:<br class="gmail_msg" />
<br class="gmail_msg" />
> Strideable? I didn't think Strideable itself was going away. I'd be sad if<br class="gmail_msg" />
> it did; for one, all the Unsafe*Pointers are Strideable and that has its<br class="gmail_msg" />
> uses.<br class="gmail_msg" />
<br class="gmail_msg" />
Nobody's proposing to remove Strideable.<br class="gmail_msg" />
<br class="gmail_msg" />
--<br class="gmail_msg" />
-Dave<br class="gmail_msg" />
<br class="gmail_msg" />
_______________________________________________<br class="gmail_msg" />
swift-evolution mailing list<br class="gmail_msg" />
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg" />
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg" /></blockquote>
</div>
_______________________________________________<br />
swift-evolution mailing list<br />
swift-evolution@swift.org<br />
https://lists.swift.org/mailman/listinfo/swift-evolution<br /></blockquote>
</div>
</body>
</html>