Looks like both those cases are supported based on similar tests here:
https://github.com/apple/swift/blob/master/test/Parse/multiline_string.swift
Should be available in snapshots
`swift-4.0-DEVELOPMENT-SNAPSHOT-2017-05-09-a` onwards.
On Wed, 31 May 2017 at 13:59 Nathan Hawes via swift-dev
wrot
I ended up writing some convenience APIs to perform these conversions along
with many other useful SourceKit<->Cocoa conversions like line+column,
UTF-8, UTF-16 and String.Index in SourceKitten. It's MIT-licensed so feel
free to grab the String extensions from the project yourself:
https://github.c
Before SourceKit-related functionality can be considered for inclusion in
release packages for Linux, it needs to be able to be built during "normal"
invocation of the build script. I say normal because it's possible to build
SourceKit with two (simple) invocations of the build script at the moment
Made a PR to update the SwiftPM side of things:
https://github.com/apple/swift-package-manager/pull/601
On Fri, 12 Aug 2016 at 18:33 wrote:
> [FAILURE] oss-swift-incremental-RA-linux-ubuntu-15_10 [#7280]
> Build URL:
> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/7280/
>
Mishal Shah
>
> On Aug 11, 2016, at 10:10 AM, Jean-Pierre Simard via swift-dev <
> swift-dev@swift.org> wrote:
>
> Apologies if this is being tracked elsewhere, but I started getting these
> failures when building the toolchain on Linux.
>
> I triggered this by runnin
Apologies if this is being tracked elsewhere, but I started getting these
failures when building the toolchain on Linux.
I triggered this by running utils/update-checkout --clone &&
utils/build-toolchain local.swift on a fresh machine. All other tests pass (
8457/8459).
Any thoughts as to why thi
any case, swift-dev isn't the best place to discuss this, so I'll
synthesize my thoughts into a swift-evolution proposal shortly.
On Mon, Dec 7, 2015 at 11:51 PM, Slava Pestov wrote:
> Hi Jean-Pierre,
>
>
> On Dec 7, 2015, at 12:21 PM, Jean-Pierre Simard via swift-dev &
> Note that I'm already working on this part. The Swift runtime needs to
provide low-level reflection interfaces that allow the standard library to
implement Mirror without depending on private runtime ABI.
That's great to hear! Is there any chance that this work could introduce
type-level reflect
