Commits

Enrico Granata committed 9abfdb372e5
Add a Mirror for UnsafePointer The one design choice here was whether to expose the pointee directly through the Mirror My choice was against that. Instead, we present UnsafePointer as UnsafePointer(0x123) and the child we expose is the 0x123 numeric pointer value The other option, of course, would be to present it as UnsafePointer(reflect(memory)) - but that seems risky to do by default UnsafePointers are allowed to be in, guess what, unsafe states, and the stakes of having playgrounds try and dereference at all times are quite too high. If the user really wants to reflect the pointee reflect(pointer.memory) will do it for them - and then any crashes will be theirs to enjoy. Of course, I am very open to arguments as to why reflect(memory) would be a better choice. Swift SVN r19386