typerep-map

typerep-map copied to clipboard

Add GHC 9.4 support

1

parsonsmatt

Manage unsafe coercions more carefully

1

Instead of using `Any`, use `TypeRep Any` or `f Any`. This makes it considerably easier to see what each coercion is actually doing. It also allows the compiler to use...

treeowl

The extra implementations of `TypeRepMap` generally has worse performance and adds dependency footprint, especially the `vector` dependency that *takes a decade* to build. Could we not build them by default?

re-xyr

Write function O-notation in prettier way using latex

8

Haddock supports that.

chshersh

Refactor (Fingerpring, Any, Any) to a data type

1

It would be better to have a special data type for this. And also special functions to convert to this datatype. This should improve code readability. And, possible, performance, if...

chshersh

Use 'inspection-testing' to guarantee that implementation for `TMap` is as efficient as for `TypeRepMap`

8

chshersh

toPairs :: TypeRepMap f -> [(SomeTypeRep, WrapTypeable f)]

5

Currently we can get the first half of this via `keys` and the second via `toList`, but I see no permanent guarantee that those have the same ordering (it's implied...

akhra

Try branch-free version of Eytzinger binary search

4

chshersh

Add Backpack interface for typerep-map

2

Especially useful when we will expose `Map`-based solution. This will also allow us to refactor tests and benchmarks. We don't need to implement all functions for every solution, for non-interesting...

chshersh

Probably do it only after multiple public library support is added to `cabal`. Also, maybe it will become possible to abstract interface with Backpack and remove code duplication in benchmarks...

chshersh