go-pulse/ethstate
obscuren 70f7a0be11 Use the state instead of the state object directly.
If a state gets reset and you still hold a pointer to the previous,
incorrect, state object you'll operate on the wrong object. Using the
state to set/get objects and attributes you won't have this problem
since the state will always have the correct object.
2014-10-16 13:38:21 +02:00
..
.ethtest Refactored state, state object and vm 2014-07-22 11:54:48 +02:00
dump.go Improved catching up and refactored 2014-09-15 15:42:12 +02:00
errors.go Refactored state, state object and vm 2014-07-22 11:54:48 +02:00
manifest.go Removed the "Get" part 2014-08-18 10:17:45 +02:00
state_object.go Use the state instead of the state object directly. 2014-10-16 13:38:21 +02:00
state_test.go ethstate.NewState => ethstate.New 2014-08-04 10:42:40 +02:00
state.go Use the state instead of the state object directly. 2014-10-16 13:38:21 +02:00