Just to clarify, is the current implementation producing a different hash from the proposed cleaner implementation?
@JohnEstropia commented on GitHub (Apr 4, 2019):
Just to clarify, is the current implementation producing a different hash from the proposed cleaner implementation?
Just checked with the unit tests, both codes seem to produce the same hash so technically neither is "Incorrect". The new syntax is ideal though so I'll be updating this in the next version.
@JohnEstropia commented on GitHub (Apr 4, 2019):
~Just checked with the unit tests, both codes seem to produce the same hash so technically neither is "Incorrect". The new syntax is ideal though so I'll be updating this in the next version.~
I see, this is during printing. Thanks! I'll also add this in the unit tests as nothing checks it right now.
@JohnEstropia commented on GitHub (Apr 5, 2019):
I see, this is during printing. Thanks! I'll also add this in the unit tests as nothing checks it right now.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @dr-mobiblocks on GitHub (Apr 2, 2019).
https://github.com/JohnEstropia/CoreStore/blob/0e254867b620107f38d06fc33e13838a2eec651a/Sources/CoreStore%2BCustomDebugStringConvertible.swift#L1017-L1022
Proposed change:
@JohnEstropia commented on GitHub (Apr 4, 2019):
Just to clarify, is the current implementation producing a different hash from the proposed cleaner implementation?
@JohnEstropia commented on GitHub (Apr 4, 2019):
Just checked with the unit tests, both codes seem to produce the same hash so technically neither is "Incorrect". The new syntax is ideal though so I'll be updating this in the next version.@dr-mobiblocks commented on GitHub (Apr 4, 2019):
Yes, it is producing a different hash 'format'.
XCode 10.2 console ouput after a schema change
Current:
Before migrating to Swift 5 and proposed implementation:
@JohnEstropia commented on GitHub (Apr 5, 2019):
I see, this is during printing. Thanks! I'll also add this in the unit tests as nothing checks it right now.
@JohnEstropia commented on GitHub (Apr 5, 2019):
Fixed in CoreStore 6.3.1