In defense of MemoryLayout<T>'s "less clarity", the people who know enough to use that stuff won't have trouble understanding it.
That said, while I like it, I'm mostly interested in sequestering this stuff away in a type as a step towards a some sort of vague macro system. Since that's obviously out of scope for, well, everything, I'm +1 regardless. - Dave Sweeris > On Jun 3, 2016, at 16:11, Erica Sadun via swift-evolution > <[email protected]> wrote: > > Discussion has more or less drawn down. Are there any further significant > requests / issues that need addressing? Both standalone functions (my > recommended approach) and the MemoryLayout<T> struct approach (alternative, > with reasons why I think it's not as ideal) are discussed in-proposal. > > Pull Request: https://github.com/apple/swift-evolution/pull/350 > > Thanks, -- Erica > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
