thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (THRIFT-3773) Swift Library
Date Wed, 21 Dec 2016 03:15:58 GMT


ASF GitHub Bot commented on THRIFT-3773:

Github user nsuke commented on a diff in the pull request:
    --- Diff: lib/swift/ ---
    @@ -0,0 +1,217 @@
    +Thrift Swift Library
    +Licensed to the Apache Software Foundation (ASF) under one
    +or more contributor license agreements. See the NOTICE file
    +distributed with this work for additional information
    +regarding copyright ownership. The ASF licenses this file
    +to you under the Apache License, Version 2.0 (the
    +"License"); you may not use this file except in compliance
    +with the License. You may obtain a copy of the License at
    +Unless required by applicable law or agreed to in writing,
    +software distributed under the License is distributed on an
    +KIND, either express or implied. See the License for the
    +specific language governing permissions and limitations
    +under the License.
    +Brought to you by [FiscalNote, Inc](
    --- End diff --
    AFAICT, there is no hard rule for this but it has never happened for us before either.
    So for it to happen we would need a policy for our project first.
    Feel free to start a discussion in mailing list.

> Swift Library
> -------------
>                 Key: THRIFT-3773
>                 URL:
>             Project: Thrift
>          Issue Type: New Feature
>          Components: Swift - Library
>            Reporter: Thomas Bartelmess
>            Assignee: Chris Simpson
> We already have the option to generate Swift code in the Cocoa compiler, however large
parts of the (Objective-C) Cocoa Library still depend on Cocoa and  Objective-C.
> It would be good to have a native Swift library that doesn't depend on the Cocoa libraries.
> Design goals:
> - Fully compatible with the code that is currently generated by the Cocoa compiler (both
Objective-C and Swift).
> - Ability to run on Linux
> - Pure Swift, no Objective-C code.
> - No dependencies on closed source apple libraries
> - Keep the same interface, so that the library is compatible with the code the current
cocoa compiler generates
> - Better server support that the current Objective-C library.
> - Follow the new Swift packaging format to be compatible with the Swift Package manager

This message was sent by Atlassian JIRA

View raw message