Re: [swift-evolution] [Discussion] Swift for Data Science / ML / Big Data analytics

> On Nov 1, 2017, at 21:13, Chris Lattner via swift-evolution > wrote: > >> On Nov 1, 2017, at 3:20 AM, Richard Wei > > wrote: Since you bring it up, Python exceptions will be annoying - As with other

Re: [swift-evolution] [Discussion] Swift for Data Science / ML / Big Data analytics

> On Nov 1, 2017, at 3:20 AM, Richard Wei wrote: >>> >>> Since you bring it up, Python exceptions will be annoying - As with other >>> languages, Python can throw from an arbitrary expression. Modeling >>> everything as throws in Swift would be super-annoying and unergonomic

Re: [swift-evolution] continuations - "extensions on steroids" idea

I suggested something similar a little while ago: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170327/034767.html ___ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution

Re: [swift-evolution] “Integer” protocol?

> On Nov 1, 2017, at 14:54, Kelvin Ma via swift-evolution > wrote: > > > >> On Wed, Nov 1, 2017 at 12:15 PM, Xiaodi Wu via swift-evolution >> wrote: >>> On Wed, Nov 1, 2017 at 07:24 Daryle Walker wrote: >> >>> >>>

Re: [swift-evolution] “Integer” protocol?

On Wed, Nov 1, 2017 at 12:15 PM, Xiaodi Wu via swift-evolution < swift-evolution@swift.org> wrote: > On Wed, Nov 1, 2017 at 07:24 Daryle Walker wrote: > >> >> >> Sent from my iPad >> >> On Oct 31, 2017, at 10:55 PM, Xiaodi Wu wrote: >> >> Right, these

Re: [swift-evolution] continuations - "extensions on steroids" idea

> On Nov 1, 2017, at 11:09 AM, Mike Kluev via swift-evolution > wrote: > > On 1 November 2017 at 15:31, BJ Homer > wrote: > Again, though, “anyone” here only means “anyone working in the same module”. > Which is a

Re: [swift-evolution] continuations - "extensions on steroids" idea

On 1 November 2017 at 15:31, BJ Homer wrote: > Again, though, “anyone” here only means “anyone working in the same > module”. Which is a very restricted set of “anyone”: it only includes > people who already have full access, and could just modify the original > struct anyway.

Re: [swift-evolution] Logging facade

Hi Maik, I believe you are looking for the «one true way of doing logging» that is community accepted, but it does not have to be in the standard library to be that. A standalone package would do just as well. swift-server-dev mailing list might be a better place to discuss this idea. Max >

Re: [swift-evolution] [draft] Target environment platform condition

> On Oct 27, 2017, at 5:06 AM, Karl Wagner via swift-evolution > wrote: > > Yeah, but by extension, every since compile-time flag is also an “axis of > configuration”. What makes these few worthy of special language integration > and compiler support? The

Re: [swift-evolution] “Integer” protocol?

On Wed, Nov 1, 2017 at 07:24 Daryle Walker wrote: > > > Sent from my iPad > > On Oct 31, 2017, at 10:55 PM, Xiaodi Wu wrote: > > Right, these issues were discussed when the proposal was introduced and > reviewed three times. In brief, what was once proposed

Re: [swift-evolution] continuations - "extensions on steroids" idea

> On Nov 1, 2017, at 8:54 AM, Zach Wolfe via swift-evolution > wrote: > > I like what this idea attempts to do, but have you thought of simply allowing > extensions of types within the same module to access private members and > declare stored properties? The

Re: [swift-evolution] continuations - "extensions on steroids" idea

> On Nov 1, 2017, at 8:28 AM, Mike Kluev wrote: > > name and ledger are essential in this proposal. > > no name -> > no ledger (how to reference it?) -> What purpose does the “ledger" serve? I’m not sure what this even means. > anyone can write parts of your class ->

Re: [swift-evolution] continuations - "extensions on steroids" idea

I like what this idea attempts to do, but have you thought of simply allowing extensions of types within the same module to access private members and declare stored properties? Adding a whole new construct to the language—while technically not source-breaking—would in practice change what is

Re: [swift-evolution] continuations - "extensions on steroids" idea

Again, though, “anyone” here only means “anyone working in the same module”. Which is a very restricted set of “anyone”: it only includes people who already have full access, and could just modify the original struct anyway. -BJ > On Nov 1, 2017, at 9:28 AM, Mike Kluev via swift-evolution >

Re: [swift-evolution] continuations - "extensions on steroids" idea

On 1 November 2017 at 15:22, Adam Kemp wrote: > I don’t see why “parts” would need to be named. That seems overly complex > for little benefit. > > name and ledger are essential in this proposal. no name -> no ledger (how to reference it?) -> anyone can write parts of your

Re: [swift-evolution] continuations - "extensions on steroids" idea

I don’t see why “parts” would need to be named. That seems overly complex for little benefit. > On Nov 1, 2017, at 7:43 AM, Mike Kluev via swift-evolution > wrote: > >> On 1 November 2017 at 13:34, Wallacy wrote: >> Partial (like in C#) is good

Re: [swift-evolution] continuations - "extensions on steroids" idea

On 1 November 2017 at 13:34, Wallacy wrote: > Partial (like in C#) is good enough. > "partial" will not read correctly in this context: class ViewController: UIViewController { partial DataSource // ?! ... } partial DataSource of ViewController:

[swift-evolution] [Potential Idea] How to indicate a trivial strong-typedef?

Here’s a quick review of a strong-“typedef” idea I’ve mentioned here: typecopy MyNewType: OriginalValueType, AnyProtocolsIWant { // Direct member declarations // “publish MemberFromOriginalType” for all overloads (or the singular item for non-functions) // “publish

Re: [swift-evolution] continuations - "extensions on steroids" idea

Partial (like in C#) is good enough. Em qua, 1 de nov de 2017 às 09:52, Mike Kluev via swift-evolution < swift-evolution@swift.org> escreveu: > class ViewController { > part DataSource > ... > } > > part DataSource of ViewController: UITableViewDataSource { > > } > > Mike > >

Re: [swift-evolution] “Integer” protocol?

Sent from my iPad > On Oct 31, 2017, at 10:55 PM, Xiaodi Wu wrote: > > Right, these issues were discussed when the proposal was introduced and > reviewed three times. In brief, what was once proposed as `Integer` was > renamed `BinaryInteger` to avoid confusion in name

Re: [swift-evolution] continuations - "extensions on steroids" idea

class ViewController { part DataSource ... } part DataSource of ViewController: UITableViewDataSource { } Mike ___ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution

[swift-evolution] Logging facade

Hey! I haven’t found anything in the history of this mail list about this topic. What do you think about having a logging facade within the standard library (like SLF in Java)? SLF4J is not within the standard library in Java, but it is well used and I’d like to have something like that within

Re: [swift-evolution] [Discussion] Swift for Data Science / ML / Big Data analytics

> On Nov 1, 2017, at 03:14, Richard Wei via swift-evolution > wrote: > > > >> On Oct 31, 2017, at 21:31, Chris Lattner via swift-evolution >> > wrote: >> >> Also, for sake of discussion, we’d have to

Re: [swift-evolution] [Discussion] Swift for Data Science / ML / Big Data analytics

> On Oct 31, 2017, at 21:31, Chris Lattner via swift-evolution > wrote: > > Also, for sake of discussion, we’d have to figure out what the type of > MemberLookupResultType would be for Python. I can see several choices: > > 1) Make it return a "PythonObject!” >

Re: [swift-evolution] continuations - "extensions on steroids" idea

"Continuation" already means something else in computer programming. I would suggest you find another term. https://en.wikipedia.org/wiki/Continuation > On Oct 30, 2017, at 6:12 PM, Mike Kluev via swift-evolution > wrote: > > a general feeling that there are two