{"push_id":630203705,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"ca73bb30da4e5dd9fff91f0d1748c83a2dd982cd","before":"ce7f7f9f4d26a9a702f120e873986445c4c9103d","commits":[{"sha":"ca73bb30da4e5dd9fff91f0d1748c83a2dd982cd","author":{"email":"0a2e4da8f53ff496298559b7f100067ec5868c8b@chronotext.org","name":"Ariel Malka"},"message":"WrappedValue REWORK: 1) IT DOES NOT MAKE SENSE TO CAST Heap<WrappedValue> TO Handle<WrappedValue> BECAUSE WrappedValue IS MUTABLE BY DESIGN, WHICH IS NOT COMPATIBLE WITH THE NON-MUTABLE NATURE OF Handle<T>. 2) IT DOES NOT MAKE SENSE TO CAST Heap<WrappedValue> TO MutableHandle<Value> BECAUSE IT WOULD DISCARD THE “BARRIERED SET” MECHANISM. 3) heapTraced MECHANISM WAS RE-ADAPTED TO HANDLE CASES WHERE Heap<WrappedValue> IS INITIALIZED WITH A NON-MARKABLE VALUE, AND THEN UPDATED WITH A MARKABLE VALUE VIA MutableHandle<WrappedValue>. SEE JSTestBed1/TestingWrappedValue/testHeapWrappedToHandle(). NOTE: THIS IS A TRANSITIONAL SOLUTION","distinct":true,"url":"https://api.github.com/repos/arielm/jsp/commits/ca73bb30da4e5dd9fff91f0d1748c83a2dd982cd"}]}