Specifying the clang import location is what is triggering the LLDBFrontend
crash.
I think you are saying that I should not need to specify the clang include
import location to the compiler.
I've attached the unmodified SwiftProtobuf example program found in the
docs at https://github.com/apple/sw
> do {
> let data = SomeStruct()
>
> print("break here")
> } catch {
> print(String(describing: error))
> }
>
>
> On Fri, Oct 13, 2017 at 10:21 AM, Edward Connell via swift-users <
> swift-users@swift.org> wrote:
>
>> Hi Michael,
>
Hi Alex,
Yes of course using the Swift PM is what I needed to do. What was I
thinking! ;p
It worked, however SwiftProtobuf 1.0.0 does not build cleanly with Swift
4.0 due to the rework of the Strings API. I hope someone will clean that up
soon.
I appreciate your feedback and time, Ed
On Mon, Oct
at 1:00 PM, Geordie J wrote:
> Hi
>
> Am 14.10.2017 um 21:55 schrieb Edward Connell via swift-users <
> swift-users@swift.org>:
>
> Has anyone used the SwiftProtobuf module on Linux?
> https://github.com/apple/swift-protobuf
>
> I am able to successfully generate swift
Has anyone used the SwiftProtobuf module on Linux?
https://github.com/apple/swift-protobuf
I am able to successfully generate swift classes from my proto file.
However when building, the code compiles but I get a ton of undefined link
references.
I included -Xswiftc -I/home/ed/swift-protobuf/.bui
import Foundation
public class SomeClass { }
public struct SomeStruct {
public weak var someClass: SomeClass?
}
do {
let data = SomeStruct()
print("break here")
} catch {
print(String(describing: error))
}
On Fri, Oct 13, 2017 at 10:21 AM, Edward Connell via swift-users <
quot;
>
> Not sure what the problem is. It worked fine in the past.
>
> If you can think of an experiment I can try to create a simple repro case,
> please let me know.
>
> Thanks, Ed
>
> On Fri, Oct 6, 2017 at 4:34 PM, Michael Gottesman
> wrote:
>
>> It look
?
>
> Michael
>
> On Oct 6, 2017, at 11:53 AM, Edward Connell via swift-users <
> swift-users@swift.org> wrote:
>
> While trying to debug a Netlib function, LLDB is crashing
>
> I'm not sure what this assert means.
>
> *LLDBFrontend:
>
$ find ~/swift -name "*dispatch*"
/home/ed/swift/usr/lib/swift/linux/libdispatch.la
/home/ed/swift/usr/lib/swift/linux/libdispatch.so
/home/ed/swift/usr/lib/swift/dispatch
/home/ed/swift/usr/lib/swift/dispatch/dispatch.h
On Sat, Oct 7, 2017 at 9:51 AM, Lane Schwartz wrote:
> Edward,
>
> Could y
No I installed it yesterday so 10/5 was the current one
On Sat, Oct 7, 2017 at 9:36 AM, Lane Schwartz wrote:
> Do you mean 10/6? I don't see a 10/5 build.
>
> On Sat, Oct 7, 2017 at 11:26 AM, Edward Connell
> wrote:
>
>> I had the same problem with the 9/30 build, but the 10/5 build worked for
I had the same problem with the 9/30 build, but the 10/5 build worked for
me.
On Sat, Oct 7, 2017 at 9:21 AM, Alex Blewitt via swift-users <
swift-users@swift.org> wrote:
> This sounds like a bug. There were some changes recently to migrate the
> build towards CMake and it may be that they have b
While trying to debug a Netlib function, LLDB is crashing
I'm not sure what this assert means.
*LLDBFrontend:
/home/buildnode/jenkins/workspace/oss-swift-4.0-package-linux-ubuntu-16_04/swift/lib/SILOptimizer/Mandatory/AccessEnforcementSelection.cpp:613:
(anonymous namespace)::SourceAccess (anonym
Ed
On Tue, Oct 3, 2017 at 11:38 AM, Vladimir.S wrote:
> On 03.10.2017 19:02, Edward Connell via swift-users wrote:
>
>> Hi All,
>> Sorry something strange happened with the first post, so I am reposting
>> this.
>>
>> I've recently wrapped up an ML frame
Hi All,
Sorry something strange happened with the first post, so I am reposting
this.
I've recently wrapped up an ML framework research project that I've been
working on for some time.
It addresses a lot of difficult design problems, and works around a lot of
compiler bugs and Linux library defici
Hi All,
I've recently wrapped up an ML framework research project that I've been
working on for some time.
It addresses a lot of difficult design problems, and works around a lot of
compiler bugs and Linux library deficiencies.
It's written almost entirely in Swift 4.0 with some C and Cuda kernels
I reported it 5/16 in bug reporter. Possibly that was the wrong DB?
https://bugreport.apple.com/web/?problemID=26535526
On Mon, Aug 28, 2017 at 8:45 AM, Joe Groff wrote:
>
> > On Aug 27, 2017, at 10:57 AM, Edward Connell via swift-users <
> swift-users@swift.org> wro
. You can see how the
> memory stacks!
>
> Now. As to why and IF Swift is INTENDED to do this, or if indeed you’re
> doing something unintended too I cannot say.
>
> If any of the above is incorrect, please chime in.
>
> Peter Nicholls
> First time post.
>
> > On
I reported this about a year ago, but it has never been fixed and it seems
like it should be fixed for the Swift 4.0 release.
Here is a simple repro case. If you watch the memory monitor as it runs,
you see memory consumption climb to 2.7GB when using #function, and no
memory increase when using a
I have been blocked for several weeks with this LLDB crashing bug, but it
has not been assigned to anyone.
I'm providing repro steps with the LLDB CLI in order to remove any
possibility that it is caused by my IDE. I have had this independently
confirmed by one of the CLion engineers.
I logged the
It sure would be nice if the compiler supported lazy lets for structs. Any
idea when or if this will be supported?
Seems like a nice performance win, lazy var is a pain because you can't
access arguments passed into a function without mutation complaints.
Thanks, Ed
__
I installed the June 7th Ubuntu 16.04 release and performed a clean build
with no problems.
However when I try to debug I get the following error, and then LLDB
terminates.
*LLDBFrontend:
/home/buildnode/disk2/workspace/oss-swift-package-linux-ubuntu-16_04/swift/lib/SIL/TypeLowering.cpp:1693:
con
Int8.max) + 1.0
>>
>> self = a / b
>>
>> }
>>
>> }
>>
>>
>> You will get a very fast and good quality prng using xoroshiro,
>> converting to unit range floating point and then back to uniform range int
>> if you wan
Any ideas when Foundation on Linux will support arc4random_uniform? This is
kind of an important function.
There doesn't seem to be any decent substitute without requiring the
installation of libbsd-dev, which turns out to be messy. Currently I am
doing this, but glibc random with mod does not prod
In swift 3.1.1 I was able to have the function below, which "gets" an
optional member collection of objects and calls their setModel member
function. Simple and clean using the forEach method.
public func setModel(model: Model) {
get()?.forEach { $0.setModel(*model*: model) }
}
However it no
cial keyword. Unfortunately
> this means if you have a ‘type’ already visible in scope, you have to fully
> qualify Swift.type(of:).
>
> Slava
>
> On May 19, 2017, at 11:18 AM, Edward Connell via swift-users <
> swift-users@swift.org> wrote:
>
> When running the co
When running the compiler using the "-swift-version 4" flag, the compiler
complains about creating a dynamic type. Errors are flagged from within
concrete base classes and also within protocol extensions.
*error: cannot invoke 'type' with an argument list of type '(of: Self)'*
*let
Great! Yes, changing the diagnostic message will save people from having to
ask this question.
Thanks, Ed
On Fri, May 19, 2017 at 10:30 AM, Devin Coughlin
wrote:
> Hi Ed,
>
> On May 19, 2017, at 10:10 AM, Edward Connell via swift-users <
> swift-users@swift.org> wrote:
>
I just switched to the 5/17 swift 4.0 tool chain on Linux, and I am getting
the following complaint when using swap on array elements. Is this warning
legitimate because of a copy on write issue? If so, is there some new swap
function for array elements? I realize I can turn 1 line into 3 and do th
Does anyone have an idea when this is going to be fixed? Or when support
will be implemented?
My app heavily uses collections of heterogenous plug-ins, so it's a real
pain in the neck to work around.
On Tue, May 2, 2017 at 2:08 AM, Satoshi Nakagawa via swift-users <
swift-users@swift.org> wrote:
uded from /home/ed/swift/usr/lib/swift/dispatch/dispatch.h:42:*
>> *#include *
>> * ^*
>>
>> *error: /usr/include/x86_64-linux-gnu/sys/cdefs.h:23:11: error: could not
>> build module 'SwiftGlibc'*
>> *# include *
>> * ^*
>&
Groan... I just tried to update to Swift 3.1 on ubuntu 16.04. Everything
builds fine, but when I try to debug I get the dreaded:
error in auto-import: failed to get module 'XYZ' from AST context
Everything built and debugged just fine with the previous Swift release.
I assume LLDB is unhappy abou
Putting a struct with your common vars in it seems like it wouldn't work,
because now it is a member and the vars aren't exposed on your object
directly, so the outer struct wouldn't conform to the protocols.
My original problem with inheritance is that you can't correctly adopt a
protocol on a ba
Observations about difining an object
- Structs can't inherit and classes shouldn't inherit, final concrete
types should be flat
- Protocols need to be adopted by the final concrete type, otherwise
constraint specializations aren't correctly applied
This creates a really ugly code dup
The error says ItemProtocol does not conform to ItemProtocol.
That doesn't make sense. It seems this should work fine.
// It's all clean until the last line
protocol ItemProtocol : class {
var message: String { get }
}
// heterogenious types
class A : ItemProtocol {
var message = "A"
}
class B :
My project is on Linux, so pure Swift.
So you don't think this is an issue of intentional library design, but a
recognized problem that hasn't been addressed yet?
Thanks, Ed
On Tue, Mar 7, 2017 at 8:13 AM, Jens Alfke wrote:
>
> On Mar 7, 2017, at 8:08 AM, Edward Connell wrote:
>
> My question
iPhone
> On Mar 7, 2017, at 7:59 AM, Jens Alfke wrote:
>
>
>> On Mar 6, 2017, at 11:36 PM, Rien via swift-users
>> wrote:
>>
>> On 07 Mar 2017, at 03:56, Edward Connell via swift-users
>> wrote:
>>
>> I would like to have an Array implem
I would like to have an Array implementation where I get more information
than just "the whole thing changed".
As a value type I get it, but lets say it's a list of 500 image info
structs and it's bound to UI. You change one item, now the whole array
changes and you have to rebuild the entire visua
t; it works. Anyone knows why this works in Xcode or in macOS? I thought it
> should show the same warnings as Linux.
>
> Zhaoxin
>
> On Fri, Mar 3, 2017 at 2:51 AM, Edward Connell via swift-users <
> swift-users@swift.org> wrote:
>
>> Hi Guillaume,
>> There is still
m> wrote:
>
>>
>> > On Mar 1, 2017, at 3:21 PM, Edward Connell via swift-users <
>> swift-users@swift.org> wrote:
>> >
>> > The thread sanitizer on Linux is reporting that I have race conditions
>> in libswiftcore. I eliminated enough cod
Ahh! thank you. That makes sense.
On Wed, Mar 1, 2017 at 3:29 PM, Guillaume Lessard <
gless...@tffenterprises.com> wrote:
>
> > On Mar 1, 2017, at 3:21 PM, Edward Connell via swift-users <
> swift-users@swift.org> wrote:
> >
> > The thread sanitizer on
The thread sanitizer on Linux is reporting that I have race conditions in
libswiftcore. I eliminated enough code down to this trivial example. Is
there really a race condition here or are these bogus errors?
let count = 1000
var items = [[UInt8]?](repeating: nil, count: count)
DispatchQueue.concu
use of `inout` is an implementation artifact.
On Wed, Jan 25, 2017 at 10:31 AM, Joe Groff wrote:
>
> > On Jan 25, 2017, at 10:20 AM, Edward Connell via swift-users <
> swift-users@swift.org> wrote:
> >
> > I have a data structure that calls isKnownUniquelyRefere
I have a data structure that calls isKnownUniquelyReferenced on a member.
It forces everything to be marked as mutating because of the inout
parameter, however the parameter is never mutated, it is just read right??
The reason it is inout is because a read only reference is required.
If it is trul
Swift test builds and runs the package Tests. My tests require data files
such as images to run.
With an Xcode project we can Copy Bundle Resources in the Build Phases to
include the necessary files.
How do we do this with swift test, or swift build?
I thought about a hack to manually copy the re
On OSX my application loads a bundle from the PlugIns directory. It loads
and executes perfectly.
Now I'm painfully trying to port my code to Linux, where we don't seem to
have frameworks or bundles per se. I assumed a bundle is just a dynamic lib
or module. My build creates a PlugIns directory an
build, escape each argument
> with the prefix eg:
> *`-Xswiftc -target x86_64-apple-macosx10.12` **should be:** `**-Xswiftc
> -target **-Xswiftc **x86_64-apple-macosx10.12`*
>
>
> On Mon, Oct 17, 2016 at 5:23 AM, Edward Connell via swift-users <
> swift-users@swift.org
Hi, I've written a Swift (with some C) framework the builds and runs
cleanly in Xcode 8.
A critical feature of my project is for my framework to run on MacOS, iOS,
and Linux.
I am trying to figure out how to build using the SPM so I can run on Ubuntu.
I'm not so happy with the project structure now
47 matches
Mail list logo
