swiftweekly / swiftweekly.github.io Goto Github PK

Let's use this issue for any discussion regarding Issue 38.

I'll probably be commenting here with links every once in awhile to help out. 😄

/cc: @modocache @BasThomas

i am not sure why, i am pretty new to programming, for some reason the subscribe button havenot worked for me. i am sorry if it was my fault or something . i am sharing the screenshot

Safari and Chrome render correctly.

Code: https://github.com/SwiftWeekly/swiftweekly.github.io/blob/master/_includes/footer.html

Firefox:

March

Booked: 2, 9, 16, 23 with Paul, HackingWithSwift.

Booked: March 30 with Realm.

Hi @jessesquires,

Seeing how well the french translation seems to be turning, I'd like to offer my translations to Brazilian Portuguese if you don't mind. This should hopefully help some people in my country and also help me keep in touch with what goes on in the Swift world more closely.

Let me know if this is fine by you!

Cheers!

http://danger.systems/guides/getting_started.html

http://proselint.com

just did this for jessesquires.github.io. super easy.

https://github.com/blog/2162-better-discoverability-for-github-pages-sites

Just a few ideas:

• Add avatars? (maybe via gravatar?)
• Add info about how to become a contributing author
• Link to the authors somewhere (maybe in the footer?)

Some new starter tasks:

• SR-1046: Make sure we use the same test runner executable for both the Swift and swift-corelibs-xctest builds.
• SR-1047: Test the Python used in the swift-corelibs-xctest project as part of the XCTest test suite.
• SR-1048: Build debug/release versions of swift-corelibs-xctest when building debug/release versions of Swift.

This task from last week is still up for grabs:

• SR-875: Improve regex support in the swift-corelibs-xctest test suite. This'll make it easier to write tests for that project.

Hi, what about a mention of https://github.com/SwiftJava/SwiftJava?

February is booked with Forward Swift.

sponsor:
link: https://forwardswift.com
heading: ! 'Forward Swift: March 2 in San Francisco + Free Online Workshop Access'
body: Attend a full day of cutting-edge iOS talks ranging from mirroring and introspection to watchOS. Your ticket includes free networking events with speakers/other devs, and 1 free month of online workshop access post event. Add an exclusive in-person workshops by Paul Hudson on beginning or advanced Swift, macOS, and server-side Swift while they last. Use code forward-swift-2017.

https://twitter.com/orta/status/687668665198731264

Not sure what this would do. Just run jekyll build?

SR-1421: Document the sourcekitd-test tool, which is used to quickly experiment with SourceKit. This task will involve writing a small amount of C++. You'll learn about LLVM's command line interface library and its argument parser, as well as about Swift's SourceKit.

• SR-1124: Migrate legacy Swift stdlib tests to the StdlibUnittest framework. This would make those tests easier to read and maintain. Over the course of completing this task, newcomers to Swift development would become familiar with several tools used to test the compiler. There are 35 tests in total--feel free to claim individual tests by commenting on the task.

Should be straight forward in jekyll

Currently, would use post.author for the written by field.

Written by:

• Appears below issue # and date, "Written by "

Add authors to _config.yml ?

authors:
    jesse: 
        name: 'Jesse Squires'
        url: 'twitter.com/jesse_squires'
   john:
        name: 'john appleseed'
        url: 'twitter.com/johnappleseed'

Hey Jesse - if you're OK with this, I'd like to write next week's issue!

Hello,

My name is Vlad. Our company Cleveroad have created our new swift library - CRNetworkButton. This is a send button for iOS - https://github.com/Cleveroad/CRNetworkButton

"Anytime the users click on the button, they will see the animation that informs them of the progress and completion."

Could you add it to your - Swift Weekly?

@jessesquires, are you writing issue 48? Or do you want someone else to pick it up?

https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fswiftweekly.github.io%2F&tab=mobile

Next issue by @modocache 😄

Hi,

I would like to start translating your posts in french in order to keep a regular challenge each week before writing my own stuff :)

How do you plan to integrate internationalization with jekyll ?
After searching a little bit on google, it seems that there is quite a few different ways to do it !

Cheers !

Issue tracking FR localization.

For Issue 33.

Tracking the remaining Swift 3 proposals to see what gets merged by the deadline:

• SE-0134: apple/swift#3816
• SE-0129: apple/swift-package-manager#566
• SE-0104: apple/swift#3796
• SE-0133: apple/swift#3809 / apple/swift#3838
• SE-0111: apple/swift#3837
• SE-0089: apple/swift#3761
• SE-0042: apple/swift#3836
• SE-0103: apple/swift#3853
• SE-0101: apple/swift#3854
• SE-0096: apple/swift#3878
• SE-0068: apple/swift#3866
• SE-0117: apple/swift#3882

Lots of noise from danger proselint sometimes.

http://danger.systems

https://github.com/ashfurrow/danger-proselint

https://github.com/lukeapage/node-markdown-spellcheck

/Library/Ruby/Gems/2.0.0/gems/bundler-1.13.0/lib/bundler/definition.rb:181:in `rescue in specs': Your bundle is locked to minitest (5.9.0), but that version could not be found in any of the sources listed in your Gemfile. If you haven't changed sources, that means the author of minitest (5.9.0) has removed it. You'll need to update your bundle to a different version of minitest (5.9.0) that hasn't been removed in order to install. (Bundler::GemNotFound)

Is this a recent issue, or is it me missing something?

See https://lists.swift.org/pipermail/swift-build-dev/Week-of-Mon-20161205/000780.html. Was wondering were these would fit in the Brief?

tl;dr: Because bridging via the ClangImporter is currently coupled with the presence of an Objective-C runtime.

• Original question: https://lists.swift.org/pipermail/swift-corelibs-dev/Week-of-Mon-20160905/000921.html
• Answer: https://lists.swift.org/pipermail/swift-corelibs-dev/Week-of-Mon-20160905/000924.html

Really interesting discussion; we should digest it and include it in issue 38 (#74)!

Referencing @ericasadun's tweet that was mentioned in the "Finally" section in this review.
There's a twitter account dedicated to explaining map, reduce and filter via emoji: https://twitter.com/functionalemoji

Pull out start task div, as seen in http://swiftweekly.github.io/issue-14/ as a new _include/

The Mistakes Most Swift Developers Don't Know They're Making

Swift is the new programming language created to be a modern replacement for Objective-C in iOS and OS X application development. In general, a skilled Swift developer is usually someone who is already experienced with Objective-C, and that, among other things, might lead them to write Swift code using Objective-C best practices, which can cause some bad mistakes.

In this article, Toptal Freelance Software Engineer Nilson Souto outlines the most common mistakes Swift developers should be aware of.

Will probably be useful to be able to search the site eventually

The weekly usually refers to people in the third person:

JP Simard rewrote the entire compiler to be much faster.

What happens if the author and the subject of the sentence are the same person? For example, in issue 39, I wrote:

Brian Gesiak sent a pull request to mark internal variables as final, which works around the bug in some cases.

Should I instead write this?

I sent a pull request to mark internal variables as final, which works around the bug in some cases.

On the one hand, it's weird to refer to myself in the third-person. On the other, "I" isn't in line with the rest of the document.

Thoughts? 🙌

not sure why
https://travis-ci.org/SwiftWeekly/swiftweekly.github.io

Referencing tweet: https://twitter.com/jesse_squires/status/797518315048448000

Hey! I'd love to help out with the new issue.

https://github.com/apple/swift/pull/4690/files

😮

I don't think is is s braking change in 2.2. I thought I read that it was just additive so that both types alias and associated type would compile in 2.2 I maybe be wrong.

Loïc Lecrenier's proposal, "Replace typealias keyword with associatedtype for associated type declarations", has been accepted for Swift 2.2! This is a breaking change, but it should be easy to migrate your existing code.

@modocache @jpsim

Hello good sirs! Thanks so much for helping out in September 😊

Here's the current tentative plan:

• Issue 37, Sept 8: Jesse
• Issue 38, Sept 15: JP
• Issue 39, Sept 22: Brian
• Issue 40, Sept 29: Brian

Of course, we can tweak this however we want. Or, if you know someone else who would like to contribute, that would work too. Let me know how this sounds! 😄