(Filed as https://bugs.swift.org/browse/SR-5344)
The following fragment appears to cause memory usage to grow unboundedly:
enum E { case A; case B(String) }
while true { var output = ""; dump(E.A, to: &output) }
I think that the issue is that when swift_EnumCaseName() is called
with an enum type
On Tue, Apr 26, 2016 at 8:49 AM, John McCall via swift-dev
wrote:
>
> I think it's reasonable to assume that @_silgen_name is not being used for
> objects that are external to the declaring module. That is, the
> implementation model is that those declarations really are declaring a Swift
> funct
On Wed, May 11, 2016 at 9:23 AM, Saleem Abdulrasool via swift-dev
wrote:
>
> Unfortunately, ATM, the runtime is compacted into the stdlib, which has the
> small problem of making the stdlib have references to the runtime functions
> as if it were being dynamically linked. We *could* just assume t
