[swift-dev] Compiler crash: is this a bug in Swift or Xcode?

When I put these two lines in a Swift file in Xcode (8.1), I get both “SourceKitService quit unexpectedly” and “lldb-rpc-server quit unexpectedly”: func f(_ a: Int, _ b: Int) { } func f(_ ab: (Int, Int)) { } Where should I file a bug report? Nevin ___

Re: [swift-dev] Compiler crash: is this a bug in Swift or Xcode?

Thank you both. Nevin On Thu, Nov 10, 2016 at 6:57 PM, Jordan Rose wrote: > > On Nov 10, 2016, at 11:19, Joe Groff via swift-dev > wrote: > > > On Nov 10, 2016, at 10:48 AM, Nevin Brackett-Rozinsky via swift-dev < > swift-dev@swift.org> wrote: > > When I pu

Re: [swift-dev] What can you change in a fixed-contents struct?

On Tue, Sep 5, 2017 at 6:08 PM, Slava Pestov via swift-dev < swift-dev@swift.org> wrote: > We expect that “define your struct in C” is still the way to go for layout > compatibility with other languages and systems. > Are there plans (however tentative) to eventually make it possible to specify t

[swift-dev] Function overload resolution

I recently got bit by SR-2450 , and I’d like to try to fix it. However, I’ve never worked on the compiler before and I have some questions: 1. Is this a reasonable first bug to tackle? 2. What resources are available for newcomers to the Swift project? 3. Wha

Re: [swift-dev] Function overload resolution

#x27;Swift.' to reference the global function in > module 'Swift' > > return min(1,2) > >^ > >Swift. > > What version of Swift are you still seeing the bad diagnostic in? > > ~Robert Widmann > > > On Sep 24, 2017, at

Re: [swift-dev] Function overload resolution

refers to instance method >> 'min()' rather than global function 'min' in module 'Swift' >> > return min(1,2) >> > ^ >> > >> > repl.swift:4:16: note: use 'Swift.' to reference the global function in >> mod

Re: [swift-dev] Function overload resolution

On Wed, Sep 27, 2017 at 12:23 PM, Jordan Rose wrote: > > > This is *definitely* a change that would need to go through > swift-evolution. There are a number of potential issues and possibilities > for breaking existing code that’s relying on this shadowing behavior, > intentionally or unintentiona