Re: [swift-dev] how to write package.swift if i want to use dependency file in local?

I am assuming by downloaded you meant Downloaded the zip from github. Suppose you have all three downloaded side by side some-dir ├── PlayingCard ├── FisherYates └── DeckOfPlayingCards since you downloaded as a zip and not cloned these directories will not be under git version control anymore. p

Re: [swift-dev] Documentation

I completely agree. SwiftDoc is great, and I really appreciate Nate's work in creating it. It's already very useful and is (IMHO) the prettiest programming language docs site I've seen. On Wed, Jan 6, 2016 at 9:52 PM, Erica Sadun wrote: > These things are achievable, in my opinion. At a minimum,

[swift-dev] how to write package.swift if i want to use dependency file in local?

hi all   i want to build dealer project in swift package-manager.because my ubuntu is not supported to connect github.so i dowload playingcard,fisheryates,deckofplaycards projects in local.build playingcatd and fisheryates successfully. how i shuold change the package.swift in deckofplaycard

Re: [swift-dev] Documentation

These things are achievable, in my opinion. At a minimum, it's worth pinging Nate to have him join in on the discussion rather than trying to replace a really great site that already does a large part of what people are looking for. -- Erica > On Jan 6, 2016, at 6:19 PM, Trent Nadeau via swift

Re: [swift-dev] Documentation

SwiftDoc is nice, but it doesn't quite do everything I want. The pages for protocols don't list implementing types in the stdlib, and the pages for types don't separate the methods by the protocol(s) that require them. Both are very useful when using generics so that the developer can create the be

Re: [swift-dev] C Macros and Variadic functions

It seems to me that an interesting tool in the swift toolchain would be one that could generate implementations of methods in circumstances like this, using, for instance, CPP macros as hints for function prototypes. Then again, I might be entirely wrong and I'd be happy to be corrected! Tom S

Re: [swift-dev] Documentation

Someone shared this with me swiftdoc.org you guys should have a look at it, its basically what I need. On Wed, Jan 6, 2016 at 10:37 PM, Trent Nadeau wrote: > Reposting from thread on swift-evolution: > > Big +1 from me. Rust's docs do this well too across trait implementations. > See, for exampl

Re: [swift-dev] Documentation

Reposting from thread on swift-evolution: Big +1 from me. Rust's docs do this well too across trait implementations. See, for example, https://doc.rust-lang.org/std/fs/struct.File.html. On Wed, Jan 6, 2016 at 5:22 PM, Ted kremenek via swift-dev < swift-dev@swift.org> wrote: > Hi James, > > We're

[swift-dev] Compiling into /usr/lib64 instead of /usr/lib

Is there an easy way to switch the install directory from /usr/lib to /usr/lib64. Some multilib systems like Fedora x86_64 require libraries to be placed in /usr/lib64 if they are 64-bit. Simply moving the files to lib64 breaks the install (not surprising). I glanced through some of the CMake fi

Re: [swift-dev] Documentation

Hi James, We're interested in hosting documentation on Swift.org for a variety of reasons. One motivating reason is to showcase the documentation for the version of the Standard Library that is in active development on 'master'. For example, whenever we generate a new snapshot that can be dow

Re: [swift-dev] How to remove Swift Dev snapshot (OS X)

That is the correct way to do it. Everything should be in that folder. > On Jan 6, 2016, at 5:27 AM, Ryan Lovelett via swift-dev > wrote: > > I ended up running: > > cd /Library/Developer/Toolchains > sudo rm -rf swift-2.2-SNAPSHOT-2015-12-* swift-latest.xctoolchain > > Hopefully that remo

Re: [swift-dev] Understanding runtime entry points

> On Jan 6, 2016, at 12:46 PM, Austin Zheng wrote: > > Thanks Joe, this is incredibly helpful, especially the note about how enums > are passed in 'piecewise'. To clarify, what you're seeing in EnumMirror is not the enum itself, but the _EnumMirror structure, which is itself designed to be bi

Re: [swift-dev] Understanding runtime entry points

> On Jan 6, 2016, at 12:57 PM, Austin Zheng wrote: > > Hey Slava, > > Thanks a lot for your detailed responses; it definitely helps to understand > how structs are passed to the C++ function. > > In a separate email, Joe Groff mentioned that there was a difference between > passing the enum

Re: [swift-dev] Understanding runtime entry points

Hey Slava, Thanks a lot for your detailed responses; it definitely helps to understand how structs are passed to the C++ function. In a separate email, Joe Groff mentioned that there was a difference between passing the enum value and passing a pointer to it. I think that might be the root of my

Re: [swift-dev] Understanding runtime entry points

Thanks Joe, this is incredibly helpful, especially the note about how enums are passed in 'piecewise'. re. your question: I was indeed calling the C++ function from Swift and directly passing in the enum (in pseudo-Swift): let myEnum : SomeEnumType = ... cplusplusFunction(value: myEnum, type: Some

Re: [swift-dev] Understanding runtime entry points

> On Jan 1, 2016, at 10:58 PM, Austin Zheng via swift-dev > wrote: > > Hello, > > I'm trying to better understand how calls are made between the Swift standard > library code and the runtime entry points. I've read through most of the > documentation in the repo but still have some questions

Re: [swift-dev] Understanding runtime entry points

Hi Austin, > On Jan 1, 2016, at 10:58 PM, Austin Zheng via swift-dev > wrote: > > Hello, > > I'm trying to better understand how calls are made between the Swift standard > library code and the runtime entry points. I've read through most of the > documentation in the repo but still have som

Re: [swift-dev] C Macros and Variadic functions

Apologies for the poor guidance. I had success with this path much earlier in Swift’s evolution and I’m clearly not up to date on the latest recommendations. Joe’s approach is definitely the right way to go. Kate Stone k8st...@apple.com  Xcode Low Level Tools > On

Re: [swift-dev] C Macros and Variadic functions

> On Jan 5, 2016, at 1:57 PM, Kate Stone via swift-dev > wrote: > >> On Jan 5, 2016, at 12:32 PM, Ryan Lovelett via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >> Just to be clear though the intent of my question was not to quibble >> with compiler error messages. My real question is

[swift-dev] Documentation

Is there a way of improving the documentation and hosting it on Swift instead of Apple ? Currently the Array page lists all of the things the class directly implements but doesn't include any of the methods mixed in by protocol extensions (i.e all of the methods from CollectionType). With YardDoc

Re: [swift-dev] swift_retainCount in CoreFoundation

> On Jan 4, 2016, at 12:10 PM, Tony Parker wrote: > > Hi Joe, > > I think we can probably elide CFGetRetainCount from the corelibs-foundation. > It’s almost always an anti-pattern to check a retain count anyway (as I’m > sure you’re aware since you’re trying to kill the swift version of it).

[swift-dev] Cross compiling Swift for 32 bit Linux from 64 bit Ubuntu

Hello Swift Community, I am trying to cross compile Swift for 32 bit Linux from 64 bit Ubuntu. For this purpose I have one question regarding build-script-impl . I am passing 'linux-i386' for option -- cross-compile-tools-deployment-targets but why linux-x86_64 appears in cross-tool-deployment-tar

Re: [swift-dev] How to remove Swift Dev snapshot (OS X)

I ended up running: cd /Library/Developer/Toolchains sudo rm -rf swift-2.2-SNAPSHOT-2015-12- * swift-latest.xctoolchain Hopefully that removes everything. ¯\_(ツ)_/¯ Thanks Johan! 🍻 On Tue, Jan 5, 2016, at 03:27 PM, Johan Jensen wrote: > The Package Installer installs everything into > /Lib