I am a bit curious about Pushkar’s test case; perhaps it should be added as a
test?
The SIL emitted then vs ~today looked very similar, so I was thinking the issue
might be in IRGen.
Scanning there, looks like this cured the problem:
@shajrawi https://github.com/apple/swift/pull/9452 Disable lar
From https://bugs.swift.org/browse/SR-3648, the work-around seems to be passing
-I /path/to/extracted/usr/lib/swift/clang/include when invoking swift (credit
Lukas and others, SR-3794 is more active)
So, ex. `swift -I ~/a-swift/usr/lib/swift/clang/include/`
Fortunately, the issue has only come u
Hello Eric,
Wanted to share I ran into a similar/the same error message this week
rebuilding from scratch (clean build/ on AWS Linux like CentOS): the build
stops (almost certainly) because the native SwiftGlibc module isn’t generated.
It happens near the end of the Swift build, around step 600
Hello Enrico,
Thank you for the reply!
If the goal of `Mirror` is reflection, wouldn’t the full structure of a type
need to be exposed by its `Mirror`? And even if the goal is a more limited form
of inspection, wouldn’t it still be necessary to make the default
implementation, which exposes a
Hello,
I had a question about the intended behavior/functionality of mirrors in
Swift/Swift Foundation types.
In general, should a Mirror reference all variables in a type?
I’m not sure what scope mirrors should/will have, but it does seem like some of
iterating through children has been done:
Hi Geoffrey,
Wanted to share I encountered this issue on 5/11.
(Ninja build was+is fine.)
Maybe the first 8 gyb scripts to run (I’m on a 2012 Mac Mini) are not
recognized as having finished…
As you suggest, CPU of xcodebuild, cmake, and python processes were all 0.
Regards,
Will Stanton
> On M
Hello Brent,
Thanks for pointing it out - obvious now!
Regards,
Will Stanton
> On Mar 19, 2016, at 6:43 PM, Brent Royal-Gordon via swift-dev
> wrote:
>
> Actually, the code samples I gave you *do* subtly depend on
> underestimatedCount being an underestimate, because the initial fast loop
>
Hello Brent,
Thanks kindly for the flair!
You gave cases for which `underestimatedCount()` is used:
> For sequences with easily-calculated counts, this should give us a size
> that's just right. For sequences where they can kind of estimate the right
> count (for instance, if you're decoding a
