CF Bolz-Tereick
CF Bolz-Tereick
- [ ] vectors [#144] - [ ] general primitives [#145] - [ ] hash [#146] - [ ] impersonators [#147] - [x] continuously run coverage tests [#148]
Coverage info: [impersonators.py](http://rawgit.com/samth/pycket/ee8e039672e19350472b43a5875a843c375ba0e2/pycket/test/coverage_report/pycket_impersonators.html) and [prims/impersonator.py](http://rawgit.com/samth/pycket/ee8e039672e19350472b43a5875a843c375ba0e2/pycket/test/coverage_report/pycket_prims_impersonator.html) These seem untested apart from some macro tests in `test_larger`. Can we add `test/test_impersonators.py` and add unit tests there?
Coverage info: [prims/hash.py](http://rawgit.com/samth/pycket/ee8e039672e19350472b43a5875a843c375ba0e2/pycket/test/coverage_report/pycket_prims_hash.html)
Coverage info: [prims/general.py](http://rawgit.com/samth/pycket/ee8e039672e19350472b43a5875a843c375ba0e2/pycket/test/coverage_report/pycket_prims_general.html) Untested primitives: - `byte?` - `procedure-arity?` (partially) - `procedure-arity-includes?` (partially, is bignum case even reachable?) - `procedure-struct-type?` - `procedure-extract-target` - `list*` - `assq` - `mlist` - `reverse`...
Coverage info: [prims/vector.py](http://rawgit.com/samth/pycket/ee8e039672e19350472b43a5875a843c375ba0e2/pycket/test/coverage_report/pycket_prims_vector.html) and [vector.py](http://rawgit.com/samth/pycket/ee8e039672e19350472b43a5875a843c375ba0e2/pycket/test/coverage_report/pycket_vector.html) Untested primitives: - `vector-immutable` - `vector-copy!` - `unsafe-vector*…` - `unsafe-flvector-length`
on at error that escapes to the toplevel we should print a scheme level traceback by looking at the continuations
Exact and inexact complex numbers behave quite differently in Racket. Also, inexact ones are much more efficient than exact ones. Thus the two cases should be two different classes in...
Experiment with a more direct interpretation style (maybe temporarily disabling call/cc to simplify things) and see whether it helps.
Is there an equivalent to the splitting of environments into environment structures and data for continuations?
`vmprof` has the fundamental assumption that code object addresses are unique across the runtime of the program. That is incorrect in many cases, e.g. I think the code object of...