Remove Mapper and Record safe_# due to performance costs
noticed that instantiation of Record instances is
pretty expensive (in terms of wall clock time) due to the Safe.next
call during construction.
see discussion: https://groups.google.com/group/liftweb/browse_thread/thread/f6a74d92d895f6ce/e8d3ef6ceced6ee8#e8d3ef6ceced6ee8
pretty expensive (in terms of wall clock time) due to the Safe.next
call during construction.
see discussion: https://groups.google.com/group/liftweb/browse_thread/thread/f6a74d92d895f6ce/e8d3ef6ceced6ee8#e8d3ef6ceced6ee8
Leave a comment
(In revision:c006de920eee45cc4522ecd9c1559c629dfd4eb0) use dynamic "safe_#" instead of random long
Closes #1196
Remove instance field which stored random long in Mapper and Record
in favor of pseudo unique System.identityHashCode at call time for
purpose of runSafe{} blocks
Branch: jon-nosafe-1196
Closes #1196
Remove instance field which stored random long in Mapper and Record
in favor of pseudo unique System.identityHashCode at call time for
purpose of runSafe{} blocks
Branch: jon-nosafe-1196