<div dir="ltr">Yes I did, that fixed the problem. Thank you</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 19, 2017 at 12:38 PM, Slava Pestov <span dir="ltr"><<a href="mailto:spestov@apple.com" target="_blank">spestov@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Do you have a member named ‘type’ in the current scope?<div><br></div><div>We changed the behavior of type(of:) so that it behaves like a normal declaration in the Swift module instead of a special keyword. Unfortunately this means if you have a ‘type’ already visible in scope, you have to fully qualify Swift.type(of:).</div><div><br></div><div>Slava</div><div><br><div><blockquote type="cite"><div><div class="h5"><div>On May 19, 2017, at 11:18 AM, Edward Connell via swift-users <<a href="mailto:swift-users@swift.org" target="_blank">swift-users@swift.org</a>> wrote:</div><br class="m_-2373026003009756995Apple-interchange-newline"></div></div><div><div><div class="h5"><div dir="ltr">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.<br><div><br></div><div><div><i>error: cannot invoke 'type' with an argument list of type '(of: Self)'</i></div><div><i> let newObject = type(of: self).init()</i></div></div><div><br></div><div>Has this changed?? Are we supposed to create dynamic types a different way now?</div><div><br></div><div>Thanks, Ed</div></div></div></div>
______________________________<wbr>_________________<br>swift-users mailing list<br><a href="mailto:swift-users@swift.org" target="_blank">swift-users@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-users" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-users</a><br></div></blockquote></div><br></div></div></blockquote></div><br></div>